6 ms·
Oddly, I find the opposite to be true, although I can't really think of a good way to justify why. I have a GUI emacs-server running that I can open buffers fr
by shabble 11y ago
Oddly, I find the opposite to be true, although I can't really think of a good way to justify why.
I have a GUI emacs-server running that I can open buffers from via emacsclient for "serious editing", but I often end up using vim for quick edits rather than bother with emacs[client] and context-switching.
I imagine it might be different if I could get used to running my shells from inside emacs with eshell or ansi-term, but have never had any success getting them to work right and be usable.
Actually, one reason for preferring the GUI does stand out - quite a bit more freedom in key-bindings, especiallly with ns-cmd-modifier and friends, and some C- bindings that are otherwise impractical in console mode (at least to my knowledge)
- ubernostrum 11y agoSince around 1999, my development workflow has been an IRC client, Emacs and various shells running inside a screen session. So it's not really context-switching for me -- Emacs is always live and running in there, so when I need to write or edit something, I just use it.