Earlier quoted context omitted.
I had a similar experience, but came to the opposite conclusion. I walked away replacing vim with emacs as my daily driver. Elisp is far more extensible than vimscript and evil-mode is pretty much at 1-1 feature parity with the real vim. I don't care much for the emacs movement keybindings except for the readline movement commands. > to this day I still don't see what the hype was about. Most of vim is written in C w…
Why don't you SSH _from_ Emacs? If you are editing a remote file there's usually no need to SSH and then invoke an editor. https://willschenk.com/howto/2020/tramp_tricks/
916 Days of Emacs
271–280 of 309 posts
Re: 916 Days of Emacs
#272Earlier quoted context omitted.
I had a similar experience, but came to the opposite conclusion. I walked away replacing vim with emacs as my daily driver. Elisp is far more extensible than vimscript and evil-mode is pretty much at 1-1 feature parity with the real vim. I don't care much for the emacs movement keybindings except for the readline movement commands. > to this day I still don't see what the hype was about. Most of vim is written in C w…
Why don't you SSH _from_ Emacs? If you are editing a remote file there's usually no need to SSH and then invoke an editor. https://willschenk.com/howto/2020/tramp_tricks/
Re: 916 Days of Emacs
#273Earlier quoted context omitted.
> why would a professional programmer not want to invest the time to learn to type properly: typing fast boosts your productivity significantly. I have not found typing speed to correlate well with productivity. I spend quite a lot of time thinking while coding.
This is true, but from what I've seen, not being able to touch type may also be a serious impediment to written communication. Maybe not so much for email, but very much so for anything ~real time like slack/chat. I once worked (mostly remotely) with a guy who I'm pretty sure couldn't touch type. He wrote pretty dense code and used very abbreviated class/variable/method names. But the real clue came from communicatin…
Re: 916 Days of Emacs
#274Earlier quoted context omitted.
I just run emacs on the remote server (inside tmux), emacs works great on the terminal, in fact, I don't use GUI emacs. code, orgmode, magit are just text.
I even started baking emacs into docker images we use for running debugging tools in kubernetes environments. Can quickly edit and run little scripts to do admin and operations and debugging tasks.
Re: 916 Days of Emacs
#275Why do people still use emacs and vim in this age of VS code and intellij? I’ve heard plenty of arguments, but they kind of suck to be honest. They’re more like rationalizations for why they stick to what they know. I just don’t get it. Why use inferior tools? Both are lighter weight. Big deal, buy a faster computer. It’s nothing compared to your salary. Both may let you type slightly faster and move around faster. M…
How are you sure VSCode and IntelliJ will be around in 10 years? 20 years? Why invest in learning a new tool every couple of years? How do I know MS doesn't suddenly kill VSC?
Also, why would I want to use an editor which calls home every few minutes? How can I be sure VSCode does not send my password files etc. to MS or OpenAI or whatever?
Also, Emacs extensibility and flexibility is unparalleled. I can mold it to fit _my_ workflow instead of molding myself to fit the workflow of some guys at MicroSoft.
Also, Emacs is self-documenting and has ridiculous introspection capabilities. My favorite example: do VSCode/IntelliJ have a counterpart of `view-lossage` (https://www.gnu.org/software/emacs/manual/html_node/emacs/Mi...)?
Also, the fact that Emacs is so keyboard-oriented (as others have mentioned) is not really about _objective speed_, but _subjective feeling of friction_ (and lack thereof).
Also, working with Emacs is so much fun. It's a piece of software so helpful that it almost feels like an A.I. assistant. ;-)
So, plenty of reasons for me.
Re: 916 Days of Emacs
#276I've been a hardcore vi user pretty much my entire life, but I decided to force myself to spend a year using emacs a while back just to see what all the fuss was about. When the year was over and I "allowed" myself to return to vi, it was like a huge weight lifted off my shoulders... to this day I still don't see what the hype was about. On the plus side, though, I memorized the emacs cursor movement commands, which…
The some reason is the (GNU) readline library that powers most command line editing.
Re: 916 Days of Emacs
#277Earlier quoted context omitted.
> Emacs is an operating system, not an editor what does it take for this tired and false meme to die?
Ok, it doesnt have a kernel full of hardware drivers or an implementation that runs on bare metal. That said, it covers a lot of userland and things otherwise covered by a Desktop Environment (which are often conflated with OSes). In terms of application hosting, window management, low-level system control, etc. and the fact that some brave souls have had success with running emacs as PID 1 means that it's not a mill…
There's https://github.com/whily/yalo apparently
Re: 916 Days of Emacs
#278Earlier quoted context omitted.
It sounds like they're not even aware that it was an option. Many people don't realize that emacs' default keybindings can be changed to be modal in exactly the same as vim, by using evil.
Sorry for the naive question, but if you're changing all your bindings to vim, then why use emacs at all? Is there any extra functional difference?
Re: 916 Days of Emacs
#279However that was only due to being in UNIX environments where IDE was a foreign word, and nothing compared to the likes of Borland offerings.
Nowadays there are plenty of IDE choices for UNIX like workloads, I don't miss Emacs, and basic VI knowledge is enough for editing configuration files on bare bones POSIX systems.
Re: 916 Days of Emacs
#280Oh man. I'm embarrassed to say I've been using emacs for almost 40 years and it probably accounts for 80% of my screen time. I wonder how many people know emacs predates gnu-emacs? I remember being skeptical of open source until I saw what gnu emacs could do. Then I got slightly more skeptical when I looked at the code ;-)
Anyway, I didn't do much customizing and never got used to vi when I was forced to use it. I don't think I liked the modefulness of vi. Yeah, emacs isn't very unix-y, but the unix-y text editor is ed. You kids get offa my lawn.