Commit db7e641 fixed issue #272, but unfortunately disabled the last-insertion tracker more often than intended by checking if `point-min' is `>=' the `(car evil-current-insertion)'. (Ditto, mutatis mutandis, the check on `point-max'). I think this is meant to go the other way. --- evil-common.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/evil-common.el b/evil-common.el index a4e0209..0f44105 100644 --- a/evil-common.el +++ b/evil-common.el @@ -1899,8 +1899,8 @@ The tracked insertion is set to `evil-last-insertion'." ;; insertion information may be invalid. There is no way ;; to detect this situation, but at least we should ;; ensure that no error occurs (see bug #272). - (>= (point-min) (car evil-current-insertion)) - (< (point-max) (cdr evil-current-insertion)) + (>= (car evil-current-insertion) (point-min)) + (< (cdr evil-current-insertion) (point-max)) (buffer-substring-no-properties (car evil-current-insertion) (cdr evil-current-insertion)))) (remove-hook 'after-change-functions #'evil-track-last-insertion t)) -- 1.8.3