Emacs and Screen
emacsen.livejournal.com
Emacs and Screen
1–10 of 17 posts
Re: Emacs and Screen
#2This doesn't solve one problem that sends me running to nano a lot: having very old Emacs versions (usually 21) on the server that don't work with my configuration.
Re: Emacs and Screen
#3I use emacs for long haul editing, but vi for quick edits and sysadmin work.
Re: Emacs and Screen
#4This doesn't solve one problem that sends me running to nano a lot: having very old Emacs versions (usually 21) on the server that don't work with my configuration.
You could always install a recent version of Emacs yourself even if you're not an admin, can't you? Also, don't forget the options for remote editing.
Re: Emacs and Screen
#5I use emacs for long haul editing, but vi for quick edits and sysadmin work.
$ emacs -q works pretty well for quick edits too
Re: Emacs and Screen
#6Don't do this. Instead, start emacs. Run M-x server-start. Now to edit a file, just say "emacsclient -t filename". You are instantly connected to your running emacs session, in the terminal you are currently working in. You can have an arbitrary number of these. C-x C-c closes the instance you are working in, not every instance.
I just run "emacs --daemon" when I log in, "emacsclient -c" to get my main emacs X frame, and then "emacsclient -t foo.bar" when I need to edit something. (Actually, I alias "emacsclient -t" to "ec", so "ec foo.bar".)
If you don't want to install Emacs for some reason, "mg" is a much better choice than vi or nano.
Re: Emacs and Screen
#7I use emacs for long haul editing, but vi for quick edits and sysadmin work.
That's just silly. mg is much nicer.