News for hackers. Stuff that matters.
Re:EmacsConf 2024 Notes by iLemming on Sunday December 29, 2024 @02:55AM (#42538410)
You don't "exit" Vim, tis not a stage - you quit it. And then go to Emacs because tis a killer, a vocation from which there's no quitting - it is for life.
Re:EmacsConf 2024 Notes by alfiedotwtf on Sunday December 29, 2024 @06:04AM (#42539214)
It’s wild doing the following on a shared production machine. I’ve seen 30+ sessions unattended for days:

    ps aux | grep vi
People not knowing how to quit vim is a meme but at the same time is real as ever.
Re:EmacsConf 2024 Notes by o11c on Sunday December 29, 2024 @08:49PM (#42545593)
I've probably had 10+ myself just because I have multiple half-finished projects open.
Re:EmacsConf 2024 Notes by pjmlp on Sunday December 29, 2024 @10:34AM (#42540534)
Maybe my error was XEmacs instead, I only put up with it until IDEs finally became part of UNIX culture.
Re:EmacsConf 2024 Notes by iLemming on Sunday December 29, 2024 @11:00AM (#42540704)
For non-emacs nerds who didn't get the joke - command for exiting Emacs is 'M-x kill-emacs', also, you don't "delete-word" in Emacs, command for it is 'kill-word', there's also 'kill-paragraph' and so on.
Re:EmacsConf 2024 Notes by trelane on Sunday December 29, 2024 @01:44PM (#42541923)
Now I wish there were a way to yank emacs after killing it.
Re:EmacsConf 2024 Notes by iLemming on Sunday December 29, 2024 @06:24PM (#42544531)
Yanking Emacs back to life? What kind of digital paganism is that? The Church or Emacs dictates using the mighty Daemon to summon it back to life.