... h3. XEmacs in Brief
* Run Gnu "screen" immediately after login to defeat SIGHUP on logout.
* Run "DISPLAY=macosx:0 xemacs -nw" to initialize your Emacs session.
* Run M-x gnuserv to allow additional X11 connections.
* Now, run "DISPLAY=macosx:0 gnuclient" to create a "real" window.
* At this point, you can close your Terminal window. Only the ssh connection will go away.
* (If you want, minimize the Terminal window. It is useful for just one thing: If XEmacs hangs in an I/O connection, perhaps to a flaky server, use the screen tty to hit it with a hard Control-G. Your Emacs might stop itself and return to the shell. If so, say "fg" to foreground it, and then tell it _not_ to autosave or abort.)
* Set up your Emacs environment as desired.
* Take a VMWare snapshot here, and reuse it for weeks and weeks. |
...
Much of this can be shell-scripted (and/or Emacs-scripted) to reduce fumbling.
Some or all of the "DISPLAY=" stuff might be optional. Do "echo $DISPLAY" before issuing a command to see if it is already set properly.
h4. Trouble Shooting
If the "gnuserv-start" command appears to do nothing, run the following shell command and look for error messages:
{noformat}
/opt/SUNWspro/contrib/xemacs-21.4.12/lib/xemacs-21.4.12/i386-pc-solaris2.8/gnuserv
{noformat}
The gnuclient man page has more information on setup than you probably want.
h4. An Emacs in Every Server
These techniques also work nicely (with adjustments) on Solaris instances which are external to your Mac. For example, if your intranet has a compute server that allows remote login, use "screen" and "gnuclient" to set up a persistent XEmacs session. There is probably no "snapshot" function available, but the session will last as long as the server stays up. (How long? That is an issue to take up with your friendly neighborhood sysadmin....)
h3. Other X11 Applications
(Recount your adventures here...)
|