From 43f44bbab3c3a6b3f219d8a1a235ee5c7267b2f5 Mon Sep 17 00:00:00 2001
From: Maxime Coste <frrrwww@gmail.com>
Date: Thu, 7 Aug 2014 21:51:36 +0100
Subject: [PATCH] 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.
---
 src/input_handler.cc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/input_handler.cc b/src/input_handler.cc
index 9459dd74..1ece72b6 100644
--- a/src/input_handler.cc
+++ b/src/input_handler.cc
@@ -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());