future of the project

[nnako]

Hi Marc,

I was wondering if you had any plans to continue development of this nice piece of software. During the last few years, there were many different approaches to solve the same issue "make vim input scheme available for all windows applications". Here are some I had a brief look into. Some seem abandoned, some show recent changes here on GitHub:

• viatc
• autohotkey-viper - this is your project
• vim_ahk
• vim.ahk
• vimulate-ahk
• autokey-autohotkey-vim-nav

As I am about to develop a solution which tries to implement APPLICATION-SPECIFIC keyboard sequences for common functionalities in a modular way, I would be interested to know if you intend to or already have proceeded working on this, yourself. Here is my solution of a superficial feature evaluation for autohotkey-viper:

Maybe, by now you stopped using vim and fiddling around with these little things due to changed life circumstances and the enlightment that time is too precious to be wasted with this... ;-)

I would be happy about an answer from you. Maybe you could confirm or correct the feature guesses made.

Thanks.
Nnako

[DavidGretzschel]

@nnako
I'm not Mark but also am trying this out.
"application sensitive-modular bindings" shouldn't be too hard to add yourself after playing with #IfWinActive for a while and then adding stuff in the right place.
Though I haven't quite figured out where that place is, still trying to make sense of the structure.

I'd love to work on that, but the main problem with autohotkey_viper is that it disables the ability to press the #-key in insert (or normal) mode. And I have absolutely no idea why yet.