Re: gutter fixes

Installation appended at end. *** Initial experiences *** (1) Start up. Tab shows up for *scratch* (I forget the exact timing). (2) Use menu to start vm. Pop up new frame; tab starts continuous flashing described by steve, on ` *vm-wconfig*'. I haven't got *scratch* back on that tab yet, nor have any of the other buffers showed up yet. (3) Switch VM menubar to XEmacs, pull down the menus for Custom, flashing starts on VM frame only. Let menus go, flashing continues and XEmacs stops responding to input until flashing stops. (4) Open new frame. Do M-X describe-installation, then C-X 1. *Help: Installation* buffer displayed, but there is only one tab, *scratch*. *** Random observations *** There doesn't seem to be any rhyme or reason as to which tabs show up on any given frame. In reading mail, I generally have multiple VM frames open, one for each mailbox I'm working on. What would be nice would be a way to define a "lead buffer" (probably the mailbox Summary) which would pull all the other associated buffers and windows that VM provides with it. It would be nice if I could do something like cvs update 2>&1 > update.log; xemacs `grep '^C ' update.log | cut -b 2-` and have all the command line arguments appear in a frame as a single "tab group" (semantics obvious, I hope). Sometimes it might be nice to have tabs on more than one window in a frame. Eg, I might split the window above, and the two or three .h files that I have personal versions of would be one tab group, and the files with CVS conflicts would be another. I think the three observations above can be summed up as "tabs should be used to page through a well-defined and well-partitioned workspace." That means buffer selection is the right application, but it shouldn't be restricted to the global list; there should be a list that is local to devices, frames, or windows. Yeah, buffers too---if you pull up a buffer in new frame (C-x 5 b), the frame ought to inherit the buffer's tab group. (Ie, the tab group might be implemented as a specifier.) I find that with the default colors the tabs, especially the selected one, are insufficiently visually distinguished. Tab customization looks to be a hard issue (anything with specifier-like behavior seems hard). *** Installation *** uname -a: Linux tleepslib2 2.2.10 #1 Sat Jul 10 12:02:27 JST 1999 i586 unknown ./configure '--prefix=/playpen' '--exec-prefix=/playpen/plat' '--with-mule' '--with-xim=xlib' '--with-xfs' '--use-union-type=yes' '--debug=yes' '--with-dialogs=athena' '--cflags=-g -O3 -fno-caller-saves -DBASKIN_ROBBINS_CHAR -L/lib -Wall -Wno-switch' XEmacs 21.2-b19 "Shinjuku" configured for `i586-pc-linux'. Where should the build process find the source code? /playpen/src/xemacs-21 What installation prefix should install use? /playpen What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -fno-caller-saves -DBASKIN_ROBBINS_CHAR -L/lib -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Using XFontSet to provide bilingual menubar. Compiling in support for Canna on Mule. Compiling in support for the WNN input method on Mule. Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Athena native widgets. Using Athena dialog boxes. Compiling in DSO module support. movemail will use "dot-locking" for locking mail spool files. Using the union type for Lisp_Objects. Compiling in extra code for debugging. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."