Git time machine keybindings clashing with evil

[rahulmutt]

If I use 'SPC g t' to access git timemachine and go back certain commits and want to search within that commit either with C-s or /, I am unable to move between commits anymore. Before search, 'N' means to go to a previous commit in the timemachine microstate. After search, 'N' will take you to previous search results. I think this means by pressing / I have canceled the microstate, but the display of the microstate is still shown below and it permanently stays there even after killing the timemachine buffer. And if I try to revive the microstate by pressing 'SPC g t' again it takes me to the first commit so I have to start all over again.

[StreakyCobra]

Try SPC w b to refocus the micro mode.
On Dec 2, 2015 8:42 AM, "Rahul Muttineni" notifications@github.com wrote:

If I use 'SPC g t' to access git timemachine and go back certain commits
and want to search within that commit either with C-s or /, I am unable to
move between commits anymore. Before search, 'N' means to go to a previous
commit in the timemachine microstate. After search, 'N' will take you to
previous search results. I think this means by pressing / I have canceled
the microstate, but the display of the microstate is still shown below and
it permanently stays there even after killing the timemachine buffer. And
if I try to revive the microstate by pressing 'SPC g t' again it takes me
to the first commit so I have to start all over again.

—
Reply to this email directly or view it on GitHub
#4032.

[nixmaniack]

This is a bug and I doubt SPC w b re-focuses the micro-state. I have had this issue where micro-state was lying around particularly in git-blame-miro-state. There was issue around this IIRC.

As a workaround, I use (spacemacs//micro-state-close-window) to close that annoying window.

[StreakyCobra]

Ok, was on my phone so couldn't test :-)

[syl20bnr]

I believed I fixed this in develop branch. Are you on master or develop ?

[nixmaniack]

On develop I can confirm.

[d12frosted]

Should be fixed with latest major release.