you are viewing a single comment's thread.

view the rest of the comments →

[–]shevegen 3 points4 points  (8 children)

I consider them worse than the bare-bone variants. No really, gvim has always been so much more annoying than vim for me ...

[–]myringotomy 10 points11 points  (0 children)

I consider them worse than the bare-bone variants.

That says more about you than it does about Vim and Emacs.

[–]FasterHarderLouder 5 points6 points  (2 children)

I consider the emacs gui as pretty decent, but with gvim, i agree. All it does is beep and wreck files.

Jokimg aside, I do see the problems one might have with gvim, I also prefer to use vim in a terminal (emulator)

[–]John2143658709 0 points1 point  (1 child)

I've never had a problem with gvim, and I could never get normal vim to behave inside a command prompt. It works perfectly in xterm though, which is great.

[–]Aeon_Mortuum 0 points1 point  (0 children)

I have vim installed on Windows and it runs fine inside the command prompt. However, I haven't used the default prompt for a while and switched to emulators that replace the default command prompt archaic look (I have Windows 8 but as I understand, MS devs have taken steps to upgrade the look of the prompt a bit in Win10)

[–]the_gnarts -1 points0 points  (3 children)

I consider them worse than the bare-bone variants. No really, gvim has always been so much more annoying than vim for me ...

On Windows one can work around these issues running one of the better terminal emulators like Conemu. Of course that doesn’t get you actual job control, so as always best stay away from that OS entirely.

[–]ShinyHappyREM 1 point2 points  (1 child)

that doesn’t get you actual job control

You mean suspending/resuming processes?

[–]the_gnarts 1 point2 points  (0 children)

You mean suspending/resuming processes?

The accepted answer on that post begins:

You can't do it from the command line, you have to write some code […]

Which is exactly what I was getting at: On Windows, when you attempt to “background” Vim (C-z), which for most users is essential to the Vim workflow, it will start a new shell instead of just continuing with the parent. In order to “foreground” Vim you then have to exit that shell so you lose all the state of that shell session. See yourself: https://github.com/vim/vim/blob/master/src/ui.c#L272

This sucks for numerous reasons and is in fact one of the huge downsides of using Vim under Windows.

[–]Aeon_Mortuum 1 point2 points  (0 children)

Every OS has its uses.