3 ms·
I am happy to use emacs, and I deeply appreciate the fact that, for example, bash understands some of its keybindings. My biggest problem by far is that few app
by Koshkin 5y ago
I am happy to use emacs, and I deeply appreciate the fact that, for example, bash understands some of its keybindings. My biggest problem by far is that few applications I use daily do that, and so every time I switch to a web browser or when I am presented with a dialog, etc. I must remain acutely aware that I am not in emacs any more and I cannot use any of its keybindings. This does not come easy.
- codesections 5y agoIf you find yourself missing emacs keybindings in the browser, you might be interested in the Nyxt browser, which incorporates emacs keybindings (and much of emacs overall philosophy) https://nyxt.atlas.engineer https://nyxt.atlas.engineer
- jonpalmisc 5y agoA nice bonus of being on macOS is that native Cocoa applications/controls understand a handful of Emacs bindings by default, and can be tweaked [1] to understand far more Emacs keys [2]. [1] http://www.hcs.harvard.edu/~jrus/site/cocoa-text.html http://www.hcs.harvard.edu/~jrus/site/cocoa-text.html [2] https://irreal.org/blog/?p=259 https://irreal.org/blog/?p=259
- trey-jones 5y agoI think I've nearly gotten used to it, but I definitely relate. It's frustrating that c-a and c-e don't work in every application, that forward-word and backward-word don't have consistent keybindings or function in the same way in every application. There is probably a moment's hesitation every time I copy text while I consider "Is it c-c or m-w?"