Fix buffer modification check

It used to grab the next key, because the normal mode reactivation
when executing the on_next_key would trigger a timestamp check again.
This commit is contained in:
Maxime Coste 2014-08-07 21:51:36 +01:00
parent c4f0c4dee6
commit 43f44bbab3

View File

@ -69,7 +69,8 @@ public:
{
if (not context().has_client())
return;
context().client().check_buffer_fs_timestamp();
// Do not check buffer timestamp, we might already be executing the
// on next key of a buffer timestamp check.
m_fs_check_timer.set_next_date(Clock::now() + fs_check_timeout);
context().hooks().run_hook("NormalBegin", "", context());