Re:Rumors of Cmd’s death have been greatly exaggerated
by vishbar on Thursday January 05, 2017 @06:04AM
(#13326224)
I use vim in cmder occasionally. The only way I've been able to use it properly is to disable conemu hooks before I execute it.
Basically, I've defined a function my profile to:
* Save the ConEmuHooks environment variable value * Set it to "Off" * Execute vim * Reset it to the previous value
I alias this command to "vim".
It's not pretty at all, and it caused me to use Sublime or VSCode most of the time, but it worked for me.
More info here: http://conemu.github.io/en/ConEmuEnvironment.html
Re:Rumors of Cmd’s death have been greatly exaggerated
by majkinetor on Sunday January 15, 2017 @03:48PM
(#13406311)
Why would you do that when gvim is available and is ways better experience then vim ? For the sake of being shell purist ? On remote shell ?
Re:Rumors of Cmd’s death have been greatly exaggerated
by _ix on Thursday January 05, 2017 @07:48AM
(#13326679)
I'll give this a shot, but I'm unclear how the hooks affect vim or other processes-does this address all of my vim+conemu problems? Thank you, in any event.
Re:Rumors of Cmd’s death have been greatly exaggerated
by quotemstr on Thursday January 05, 2017 @11:46AM
(#13328647)
Have you tried Cygwin vim in mintty?
Also, Emacs has a mode where it'll run as a Cygwin process, but use native win32 widgets. I've found using it to be the most pleasant way of interacting with Windows systems.
When I was at Microsoft, I joked that I wasn't so much running "Windows" as GNU/NT. :-)
For a command line interface, I find it to be fairly unstable, too.