61–70 of 123 posts
The best feature of vim is its ubiquity; I feel at home on almost any computer. I find myself shying away from anything too specialized that could become a crutch, maybe to my detriment.
Same here. That is, until I find out that only vi's there and not full-on vim. While vi is smaller and even more ubiquitous, it pains me that it lacks visual mode.
Earlier quoted context omitted.
Same here. That is, until I find out that only vi's there and not full-on vim. While vi is smaller and even more ubiquitous, it pains me that it lacks visual mode.
Visual mode is a crutch! I'm used to vi so I never use it. There are faster, more flexible ways of doing anything you'd do in visual mode with plain vi commands.
Earlier quoted context omitted.
Why would you leave yourself in this low practiced state? Ie you don't spend the time to become fluent, so it's always "thinking" instead of being able to just do. Incidentally you should always always leave the insert mode when you are done typing. You are never confused about state because your default is "normal mode".
Because becoming fluent has a cost value trade off, and I think there are a lot of people who simply don't think time invested in that is worth it. I touch a terminal a lot, and I don't value vim enough to become fluent. I certainly know how to use it, and I know a fair bit of the commands, but it's nowhere close to my preferred workflow. Plus, there's a huge array of tools out there to allow me to work with files in…
Go figure.
Roguelikes, UT, Doom, Quake , and the like from my past pushed me more than anything into learning and loving emacs keyboard bindings.
No other way to experience that sort of speed-of-thought and precision in a UI/UX for me, and certain actions within emacs very much remind me of muscle-twitch maneuvers like rocket-jumping, bunnyhopping, or reload-canceling.
Earlier quoted context omitted.
How often are you in situations where you can't run the editor/IDE you want? I haven't encountered this for years except the rare times I'm forced to do some editing over SSH (which is far too low-level for server management than I'd like).
If you have to edit over SSH then you can do an sshfs mount instead. sshfs @ : ≤mountpt≥
Can you sudo over sshfs somehow without logging as root?
It uses ctrl+s ctrl+c type shortcuts and has mouse support, it really is slick.
Earlier quoted context omitted.
Visual mode is a crutch! I'm used to vi so I never use it. There are faster, more flexible ways of doing anything you'd do in visual mode with plain vi commands.
How do you compare two pieces of code side-by-side? I suppose you could create terminals and arrange then how you like but that's not much different than vim. I use gtk emacs with three frames arranged side-by-side on a 40" monitor. Not being able to compare code this way would really slow me down.
The best feature of vim is its ubiquity; I feel at home on almost any computer. I find myself shying away from anything too specialized that could become a crutch, maybe to my detriment.
emacs-nox (apt install emacs24-nox usually) is also surprisingly feature-full and comfort to work with for emacsers
sudo apt install ne
I'm afraid that the node requirement and lack of Debian repo would rule it out in many situations, like remote editing. Too much work to get it installed on ephemeral boxes. Could someone start a project like this with C and Python plugins? I'd like to contribute.
Guess I'll stick with ne or sshfs and main editor for now.
Earlier quoted context omitted.
If you have to edit over SSH then you can do an sshfs mount instead. sshfs @ : ≤mountpt≥
Almost every time I have to edit text over SSH, it is to change configuration files that aren't writable for my SSH user. Can you sudo over sshfs somehow without logging as root?
Earlier quoted context omitted.
emacs-nox (apt install emacs24-nox usually) is also surprisingly feature-full and comfort to work with for emacsers
What's the difference between emacs-nox and "emacs -nw"?