5 ms·

The great thing about vi(m) is that it's always there. SSH'd into some random server and need to edit some random config? vim. And Sublime is vim with a user-

The great thing about vi(m) is that it's always there. SSH'd into some random server and need to edit some random config? vim. And Sublime is vim with a user-friendly-ish GUI wrapped around it.

abhinav22 5y ago
Does sublime support vim keys?
- NegativeLatency 5y ago
  A lot of vim/vi plug-ins are buggy and support just enough to really drive you crazy
  - weaksauce 5y ago
    fwiw i've also thought that and moved to vscode with neovim as the backing editor for normal mode and it's generally fantastic. some rough edges but not that many... it's still neovim and vim in the background
    - NegativeLatency 5y ago
      Oh yeah well that’s a whole vim running in there. Ended up settling on MacVim.app which has nice window support. I’ve had good experiences with the visual studio vim plug-in that’s written in F#
- junon 5y ago
  Yes but I've yet to come across an implementation that gets it right.
simion314 5y ago
>The great thing about vi(m) is that it's always there. SSH'd into some random server and need to edit some random config? vim I hate that, I ssh in, then maybe I want to edit cron and I am hit with vim(someone changed the simple nano with it), in the past you had no choice then google how to quit vim but now it will tell you how to do it(I ssh and change config files 1 or 2 times a year). I never learned how to quit, just o use EDITOR=nano command to get a simple editor, I don't need a powerful editor for config files.
- ironmagma 5y ago
  A lot of times it's easier to just learn the tools of the trade instead of fighting a never-ending battle. I don't need or like awk, but I learned it because it's in use and it was very helpful to do so.
  - KronisLV 5y ago
    This leads to being stuck with tools which are unpleasant to use and sometimes not suited for what you want to do with them - for example, editing text files as a beginner. Would it be better if Nginx would have never been written and we'd all use Apache instead? What about Docker never having been written and us having to ship VM images with no tool chain around them? What about JetBrains never creating new IDEs and everyone being stuck with Eclipse or NetBeans? What about no systemd and having to use sysvinit or OpenRC? Okay, perhaps that last one is debatable, due to some valid concerns. If Vim is so powerful, then this power should be embraced and transformed into a software package that's easier to use, be it with nano style hints or simpler shortcuts - Vim isn't good because of its accidental complexity after all! Of course, that might take a few generations, because no one who knows Vim wants to relearn it, whereas the newer people will oftentimes simply resist using it. But my point is that the weaknesses of each software package should be addressed and eventually fixed, either in itself or another to replace it.
    - ironmagma 5y ago
      Any sufficiently capable editors will be complex. Emacs for example is just as hard to learn if not harder than vim. Nano is easier for one simple reason which is that it is not as capable. Could vim be easier? Probably. But it’s still useful and is an archetype. Remember I’m not saying new code should be written in Awk. It’s just useful to know how to use the tools that everyone knows, regardless of whether they should be replaced or improved. The handsaw isn’t perfect or that beginner friendly, but if you refuse to learn to use one because there are other cutting instruments, you’ll probably have a bad time compared to if you didn’t.
      - 5y ago

The great thing about vi(m) is that it's always there. SSH'd into some random server and need to edit some random config? vim. And Sublime is vim with a user-friendly-ish GUI wrapped around it.

abhinav22 5y ago

Does sublime support vim keys?

NegativeLatency 5y ago
A lot of vim/vi plug-ins are buggy and support just enough to really drive you crazy
- weaksauce 5y ago
  fwiw i've also thought that and moved to vscode with neovim as the backing editor for normal mode and it's generally fantastic. some rough edges but not that many... it's still neovim and vim in the background
  - NegativeLatency 5y ago
    Oh yeah well that’s a whole vim running in there. Ended up settling on MacVim.app which has nice window support. I’ve had good experiences with the visual studio vim plug-in that’s written in F#
junon 5y ago
Yes but I've yet to come across an implementation that gets it right.

simion314 5y ago

>The great thing about vi(m) is that it's always there. SSH'd into some random server and need to edit some random config? vim I hate that, I ssh in, then maybe I want to edit cron and I am hit with vim(someone changed the simple nano with it), in the past you had no choice then google how to quit vim but now it will tell you how to do it(I ssh and change config files 1 or 2 times a year). I never learned how to quit, just o use EDITOR=nano command to get a simple editor, I don't need a powerful editor for config files.

ironmagma 5y ago
A lot of times it's easier to just learn the tools of the trade instead of fighting a never-ending battle. I don't need or like awk, but I learned it because it's in use and it was very helpful to do so.
- KronisLV 5y ago
  This leads to being stuck with tools which are unpleasant to use and sometimes not suited for what you want to do with them - for example, editing text files as a beginner. Would it be better if Nginx would have never been written and we'd all use Apache instead? What about Docker never having been written and us having to ship VM images with no tool chain around them? What about JetBrains never creating new IDEs and everyone being stuck with Eclipse or NetBeans? What about no systemd and having to use sysvinit or OpenRC? Okay, perhaps that last one is debatable, due to some valid concerns. If Vim is so powerful, then this power should be embraced and transformed into a software package that's easier to use, be it with nano style hints or simpler shortcuts - Vim isn't good because of its accidental complexity after all! Of course, that might take a few generations, because no one who knows Vim wants to relearn it, whereas the newer people will oftentimes simply resist using it. But my point is that the weaknesses of each software package should be addressed and eventually fixed, either in itself or another to replace it.
  - ironmagma 5y ago
    Any sufficiently capable editors will be complex. Emacs for example is just as hard to learn if not harder than vim. Nano is easier for one simple reason which is that it is not as capable. Could vim be easier? Probably. But it’s still useful and is an archetype. Remember I’m not saying new code should be written in Awk. It’s just useful to know how to use the tools that everyone knows, regardless of whether they should be replaced or improved. The handsaw isn’t perfect or that beginner friendly, but if you refuse to learn to use one because there are other cutting instruments, you’ll probably have a bad time compared to if you didn’t.
    - 5y ago