4 ms·

As a long time emacs user, I can confirm that emacs is terrible... and everything else out there is deficient. I can write custom code (ew, elisp) to determine

As a long time emacs user, I can confirm that emacs is terrible... and everything else out there is deficient. I can write custom code (ew, elisp) to determine how to switch between buffers (test buffer and code under test) and I can run my tests and find operations and the like in a first class buffer and a dozen things like that which are just incredibly painful in other editors. Also I hit Cx-c by mistake thrice a week.

deleted 6y ago
[deleted]
joosters 6y ago
;;; Make it more difficult to kill emacs accidentally (defun my-kill-emacs () "Confirm before 'save-buffers-kill-emacs'." (interactive) (if (y-or-n-p "Really kill Emacs? ") (save-buffers-kill-emacs) (message "Aborted") ) ) (global-set-key "\C-x\C-c" 'my-kill-emacs)
- jimmyvalmer 6y ago
  Dude, `M-x custom-set-variable RET confirm-kill-emacs RET TAB`
  - morelisp 6y ago
    Or just unbind it, you won't typo `M-x kill-emacs`...
    - fennecfoxen 6y ago
      TBH it actually helps me a little. I seldom lose any work at all, and I have to remember to commit editor config changes somewhere persistent. :P
MarcScott 6y ago
Run Emacs as a server. You can kill the client accidentally, then just load another client instantly and carry on from where you left off.
- momentoftop 6y ago
  Exactly. My emacs uptimes (M-x emacs-uptime) are generally the same as my machine's uptime, which is typically months. Emacs is one of the most rock-solid pieces of software I have running. It's also great for remote. I have emacs daemons running continuously on my remote boxes. To start work on those machines, I log in and start my emacs client. I've never had a need for things like "screen".
  - disgruntledphd2 6y ago
    Does that actually work? My understanding is that without screen/tmux, the process will die if you disconnect the shell (on a remote box). Interesting that --daemon works too (I've been running emacs through tmux for years, and never knew that).
    - momentoftop 6y ago
      It definitely works, starting emacs with "--daemon".
TeMPOraL 6y ago
> Also I hit Cx-c by mistake thrice a week. Unbind it. Problem solved. That's what I do with my clumsy fingers.

deleted 6y ago

[deleted]

joosters 6y ago

;;; Make it more difficult to kill emacs accidentally (defun my-kill-emacs () "Confirm before 'save-buffers-kill-emacs'." (interactive) (if (y-or-n-p "Really kill Emacs? ") (save-buffers-kill-emacs) (message "Aborted") ) ) (global-set-key "\C-x\C-c" 'my-kill-emacs)

jimmyvalmer 6y ago
Dude, `M-x custom-set-variable RET confirm-kill-emacs RET TAB`
- morelisp 6y ago
  Or just unbind it, you won't typo `M-x kill-emacs`...
  - fennecfoxen 6y ago
    TBH it actually helps me a little. I seldom lose any work at all, and I have to remember to commit editor config changes somewhere persistent. :P

MarcScott 6y ago

Run Emacs as a server. You can kill the client accidentally, then just load another client instantly and carry on from where you left off.

momentoftop 6y ago
Exactly. My emacs uptimes (M-x emacs-uptime) are generally the same as my machine's uptime, which is typically months. Emacs is one of the most rock-solid pieces of software I have running. It's also great for remote. I have emacs daemons running continuously on my remote boxes. To start work on those machines, I log in and start my emacs client. I've never had a need for things like "screen".
- disgruntledphd2 6y ago
  Does that actually work? My understanding is that without screen/tmux, the process will die if you disconnect the shell (on a remote box). Interesting that --daemon works too (I've been running emacs through tmux for years, and never knew that).
  - momentoftop 6y ago
    It definitely works, starting emacs with "--daemon".

TeMPOraL 6y ago

> Also I hit Cx-c by mistake thrice a week. Unbind it. Problem solved. That's what I do with my clumsy fingers.