emacs-everywhere
emacs-everywhere copied to clipboard
Delete is rebinded in every buffer to `emacs-everywhere-erase-buffer`
When emacs-everywhere is called from terminal using emacsclient --eval '(emacs-everywhere)'
in every buffer delete gets rebinded to emacs-everywhere-erase-buffer-command
and it stays so until emacs-everywhere-mode
is enabled and disabled manually, then pressing delete key will erase buffer once and after undoing that erase key will return to normal behavior.
Steps to reproduce:
-
emacs -Q --daemon
-
emacsclient
- Install emacseverywhere
-
emacsclient --eval '(emacs-everywhere)'
- Finish using either
C-c C-c
orC-x 5 0
- Press delete in any Emacs buffer
Output of emacs-version
: GNU Emacs 28.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, cairo version 1.16.0)
Display server: x11
Distribution: NixOS 22.05 (Quokka)
Evaluating (setq emacs-everywhere-mode-initial-map nil)
as per docstring of that variable to make it so that this map never activates seems to solve issue. For me this is enough as a fix since I don't use that feature anyway. Keeping ths issue open in case there is some fix to this without disabling it.
I'm having this problem too except emacs-everywhere-erase-buffer
is binded to backspace instead of del, and it won't go away.
If I eval the expression (setq emacs-everywhere-mode-initial-map nil)
, my keyboard is locked when I finish emacs-everywhere
and I'm unable to press any key until what I found out is to press Ctrl-c anywhere in the desktop.
I'm using Doom Emacs with it.
For what it's worth, I have seen this issue but have not been able to reproduce it. The key map should only be applying locally.
I can confirm that I am also not seeing this issue in Doom Emacs + Emacs 29.
I'm on emacs-28.3 and Doom. This worked for me: (setq emacs-everywhere-mode-initial-map nil)
I am no longer having this issue in emacs master and 28.2. Since creation of issue I have updated dwm to 6.4 which could have fixed this but I have no idea if that was the cause or something else got updated/changed that resolved this for me.