Re: [Github-comments] [geany/geany-plugins] Vimode: Can't exit insert mode if 'g' was the last entered character. (#1075)

2021-09-29 Thread Frank Lanitz
Closed #1075 via #1100. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1075#event-5382297224

Re: [Github-comments] [geany/geany-plugins] Vimode: Can't exit insert mode if 'g' was the last entered character. (#1075)

2021-08-17 Thread Jiří Techet
> EDIT: I have "Insert Mode for Dummies" on. When I turned that off, it works > now. The bug is in "Insert Mode for Dummies". Ah, OK, I can reproduce it now. Will investigate. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on

Re: [Github-comments] [geany/geany-plugins] Vimode: Can't exit insert mode if 'g' was the last entered character. (#1075)

2021-08-17 Thread natopwns
It's still happening for me. I just open Geany, type `i`, type `g`, and press ``, which does nothing. As soon as I type any other character, `` sends me back to command mode. I'm using Geany from the Arch repos, maybe it has to do with that. I'll try to build from source and see if it stills

Re: [Github-comments] [geany/geany-plugins] Vimode: Can't exit insert mode if 'g' was the last entered character. (#1075)

2021-08-10 Thread Jiří Techet
I don't seem able to reproduce the problem. What exactly do you do? When I'm in command mode, enter insert mode using `i`, type `g` and press ``, I get back to the command mode. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on

[Github-comments] [geany/geany-plugins] Vimode: Can't exit insert mode if 'g' was the last entered character. (#1075)

2021-04-28 Thread natopwns
Steps to reproduce: - Enter insert mode. - Type the letter 'g'. - Try to exit insert mode. Expected behavior: Program exits insert mode. Actual behavior: Program stays in insert mode. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view