The basic vim commands I have internalized over the years are sufficient for those odd jobs. But 99% of the time, I am not on some remote machine, I am on my personal computer, so I can choose to use a tool that is not installed by default. In those situations, I also still use vim. >This has saved my ass at least twice where I couldn't access vim or had internet access to install XYZ editor. You are always just one click away from the source code implementing any functionality of your editor, which you can, if you choose to do so, modify and evaluate on the fly.Įmacs-like shortcuts are also available wherever you have readline (e.g. Vim encourages the mindset of mastery = learning a bunch of tricks, remembering them and incorporating them into muscle memory.Įmacs on the other hand encourages the mindset that my editor is a programmable tool, I am a programmer, I can make it do whatever I want. That was also me during ten years of vim usage. How many times have you opened the source code of some vim plugin you are using and tried to modify what it does? How many lines of vimscript have you written? No, copy-pasting config lines from someone's dotfiles doesn't count. Heck, I think I have the default background on my mac. I guess I garden in my garden vs my config files and am not so focused on some kind of concept of purity. And I don't feel the need to maintain a codebase for my config like I enjoyed doing in college. I'm comfortable with it and haven't ever really found it lacking. I have a smallish vim config with a handful of plugins, mostly for linting. I play with using VSCode with vi bindings from time to time, but honestly just forget to use it much. ![]() The bindings in IntelliJ are good enough, although sometimes I forget and try to do things, like run a file through awk. I use IntelliJ (and do Python and Go in it) with vi binding for large long-lived projects and just vim/neovim in a terminal for scripts, short-lived stuff, and quick edits. I find I get pissed at every text editor that isn't vi. Now I find modal editing very natural and productive and don't miss the keyboard gymnastics of emacs. The modal thing in vi(m) was hard for me to wrap my head around and the bizarre config of vim seemed so inelegant.īut when I got a gig as a sysadmin running a few thousand servers w/ a slew of Unixes (Solaris, BSD, HP-UX, Linux) I finally bit the bullet and learned vi, because it was the only common denominator (oh, man and ksh88 because so many bash-es were so broken on those platforms). Also used Sawfish as my window manager, etc. In college I used Emacs, because I had a romance with lisps and just really enjoyed extending stuff. > Improve Tramp performance to match the experience of using terminal Emacs via SSH, or VSCode’s Remote Development. What a different experience from my carefully-put-together, half-working, slow Emacs setup. ![]() ![]() Saving files was snappy and LSP worked out of the box. Getting up and running was trivial and the performance was great. On a whim, I installed VSCode for the first time and tried its “remote development” capabilities and holy smokes are they good. This has been sufficient to have me looking out again. > More recently, I’ve been very put off by the performance and stability (or lack thereof) of building large scale software via Tramp. ![]() He dived deep into finding out why that was and how to fix it, pointing out how great Emacs's introspection is that one can find solutions to problems like these.Īnd then two thirds of the way into his essay, he has this: The summary is that the author tried to open a remote file and Emacs froze for several seconds. On vim vs emacs - May 2010 (28 comments)ĭebian's Vim maintainer switches to Emacs - Oct 2008 (32 comments) How a Vim user converts to Emacs - Dec 2010 (66 comments) Some thoughts on Emacs and Vim - Feb 2011 (40 comments) Emacs Shootout and Deal - Nov 2011 (52 comments) Why I switched from Vim to Emacs - Dec 2016 (101 comments)įrom Vim to Emacs - Sept 2014 (116 comments)Įmacs and Vim - July 2014 (275 comments) Others?Īfter over a decade of Vim, I’m hooked on Emacs - March 2018 (161 comments)Ī pragmatic decision on GNU Emacs versus Vim for programming - Feb 2017 (59 comments) Just for fun, here are some of the larger past threads.
0 Comments
Leave a Reply. |