After a while of using vimpulse mode in a buffer, it gets into a strange state where if I go from vi-mode to visual-line-select mode by pressing "V", it "remembers" my previous visual-line-selection (cursor position, number lines selected and all) and takes me back to it. This is undesirable, naturally. I don't know exactly how to reproduce the bug, but have managed to record a video of it in action: http://screencast.com/t/YjBlMmVkMjQ The buggy-state is buffer-local. Killing a buffer, and then re-opening the file, restores sanity, as demonstrated in the video. Thanks for vimpulse mode! Tim
On 2010-07-20 16:12, Tim Harper wrote:
I don't know exactly how to reproduce the bug, but have managed to record a video of it in action:
Hi Tim! Welcome to the list, and thanks for the coolest bug report so far :) Let's get the basics out of the way first. Is that Aquamacs (what version?), and are you using the latest developmental commit of Vimpulse? I don't know exactly why this happens, but I've been able to reproduce it by injecting a "bad value" into one of Visual mode's buffer-local variables. It seems that somehow Visual mode isn't deactivated properly and that a faulty variable causes problems upon reactivation. The variable is remembered across Visual sessions, giving rise to a persistent "buggy state". Furthermore, as the restoration of the previous selection occurs in `post-command-hook' -- after hl-line-mode et al. have refreshed their own highlighting -- the other modes aren't able to pick up on it, and so their highlighting doesn't coincide with Visual mode's. Commit [9d1af90898] should be more robust with regard to such values. Let me know if the bug persists. -- Vegard
On Wed, Jul 21, 2010 at 3:38 AM, Vegard Øye <[email protected]> wrote:
On 2010-07-20 16:12, Tim Harper wrote:
I don't know exactly how to reproduce the bug, but have managed to record a video of it in action:
Hi Tim!
Welcome to the list, and thanks for the coolest bug report so far :)
Let's get the basics out of the way first. Is that Aquamacs (what version?), and are you using the latest developmental commit of Vimpulse?
I don't know exactly why this happens, but I've been able to reproduce it by injecting a "bad value" into one of Visual mode's buffer-local variables. It seems that somehow Visual mode isn't deactivated properly and that a faulty variable causes problems upon reactivation. The variable is remembered across Visual sessions, giving rise to a persistent "buggy state". Furthermore, as the restoration of the previous selection occurs in `post-command-hook' -- after hl-line-mode et al. have refreshed their own highlighting -- the other modes aren't able to pick up on it, and so their highlighting doesn't coincide with Visual mode's.
Commit [9d1af90898] should be more robust with regard to such values. Let me know if the bug persists.
After many attempts, I can't isolate exactly what I do that gets emacs into this state. Merged your change, no more incidents yet. Thanks! Tim
participants (2)
-
Tim Harper -
Vegard Øye