Re: gutter fixes
At 05:03 PM 8/5/99 +0900, Stephen J. Turnbull wrote:
(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.
I don't see this.
(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.
Nor this. But I'm going to commit an expose patch that might help.
(4) Open new frame. Do M-X describe-installation, then C-X 1.
*Help: Installation* buffer displayed, but there is only one tab,
*scratch*.
Fixed.
*** Random observations ***
There doesn't seem to be any rhyme or reason as to which tabs show up
on any given frame.
It should be better RSN, let me know....
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).
I agree. At the very least I would like to pull in some of the buffer
sorting code from menubar-items so that tabs are grouped better.
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.
Ouch. There's nothing to stop you doing this with tabs, but gutters are
per frame (although window local) at the moment. Thinking about it this
might be relatively straightforward to fix
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.)
Right. Although I only have 10 fingers currently, so I would *really* like
someone else to experiment with this if they have the time.
I find that with the default colors the tabs, especially the selected
one, are insufficiently visually distinguished.
I haven't checked whether the color code is working as yet.
Tab customization looks to be a hard issue (anything with
specifier-like behavior seems hard).
Yup. :)
andy
--------------------------------------------------------------
Dr Andy Piper
Senior Consultant Architect, BEA Systems Ltd