Recent Features
| |||||||||||||
Openbox: A lightweight window manager (Linux.com)Openbox: A lightweight window manager (Linux.com)Posted Feb 3, 2006 20:14 UTC (Fri) by nix (subscriber, #2304)In reply to: Openbox: A lightweight window manager (Linux.com) by zooko Parent article: Openbox: A lightweight window manager (Linux.com)
I am also a GNU screen fanatic, but it doesn't understand the full panoply of keys on the keyboard, so you have to use key sequences everywhere. I use left-windows-key and cursor keys to switch virtual desktops, and left-windows-key and , and . to switch konsoles, sort of thing.
I tend to use screen for things I want to outlast my X session (e.g. XEmacs).
(Log in to post comments)
Openbox: A lightweight window manager (Linux.com) Posted Feb 3, 2006 20:17 UTC (Fri) by zooko (subscriber, #2589) [Link] Does that mean you are running XEmacs in tty mode instead of in X mode?
Openbox: A lightweight window manager (Linux.com) Posted Feb 3, 2006 21:51 UTC (Fri) by nix (subscriber, #2304) [Link] Nah: run it with -unmapped in a screen session and run gnuserv; then connect via gnuclients with DISPLAY set. Bingo, one XEmacs, multiple displays. :)
XEmacs does not have the strict `tty mode' / `X mode' distinction of Emacs of yore; you can have frames on multiple X servers and ttys at the same time.
Openbox: A lightweight window manager (Linux.com) Posted Feb 6, 2006 17:47 UTC (Mon) by zooko (subscriber, #2589) [Link] I tried this, but couldn't figure out how to run gnuserv without a UI. So then I tried -nw to get the text-mode UI and run gnuserv-start, and then run gnuclient to create a GUI window.
Alas when the X server goes away then the xemacs server dies with an ugly internal error stack trace, which means I don't get the advantages of a "stable, persistent, remotely reachable" xemacs that I was hoping for.
I guess I could script gnuserv-start to run automatically, for example by appending it to my .xemacs/custom.el file. I'll try that...
Openbox: A lightweight window manager (Linux.com) Posted Feb 6, 2006 17:50 UTC (Mon) by zooko (subscriber, #2589) [Link] Okay, so I tried starting xemacs like this, inside screen.
xemacs -unmapped -eval "(gnuserv-start)"
This correctly started it without creating a window, and I was able to run gnuclient to connect to it and create windows. However, still when the X server goes away, the xemacs process dies with a traceback (appended). Too bad.
Fatal error (13).
Your files have been auto-saved.
Your version of XEmacs was distributed with a PROBLEMS file that may describe
*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
gdb /usr/bin/xemacs core
then type `where' at the debugger prompt. No GDB on your system? You may
Lisp backtrace follows:
# (condition-case ... . error)
Openbox: A lightweight window manager (Linux.com) Posted Feb 7, 2006 8:19 UTC (Tue) by nix (subscriber, #2304) [Link] What version of XEmacs was this? There were bugs causing this until fairly recently (and if you use Lesstif or Motif there are unavoidable bugs in those toolkits that will cause these symptoms).
Openbox: A lightweight window manager (Linux.com) Posted Feb 7, 2006 15:30 UTC (Tue) by zooko (subscriber, #2589) [Link] XEmacs 21.4 (patch 18) "Social Property" [Lucid] (amd64-debian-linux) of Wed Dec 21 2005 on yellow
If I could get your e-mail address from lwn.net, then we could move this conversation to another forum. You could write to me at <zooko@zooko.com> if you like. Thanks for your help!
I'm not sure what toolkit I'm using for my xemacs -- it is packaged by Ubuntu. I suppose if I install "xemacs21-gnome-nomule" instead of "xemacs21-nomule" then I'll get one that uses Gtk. I'll try that. Thanks!
|
|||||||||||||