From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Two GTK related feature requests
Date: Tue, 18 Nov 2003 18:03:58 -0500 [thread overview]
Message-ID: <E1AMEt4-0000Bf-Va@fencepost.gnu.org> (raw)
In-Reply-To: <87oevag25a.fsf@emptyhost.emptydomain.de> (message from Kai Grossjohann on Mon, 17 Nov 2003 20:40:01 +0000)
One thing that people seem to do is to implement scrolling, of sorts.
It looks like this (assuming only two buffers are shown):
________ ________
/buffer 3\/buffer 4\[<][>]
Then you can click on [<] to show buffers 2 and 3, and on [>] to show
buffers 4 and 5 in the tab bar. Or so, maybe the arrows scroll by
more than one buffer.
I think that's a good partial solution.
Another thing that people seem to do is to shorten long buffer names,
so that they display "som...ame" instead of "some long buffer name".
I think that's a good partial solution.
Whether these two partial solutions are enough for real usage,
I can't guess in advance.
A third thing, which is an alternative to the first thing, is that
they just show multiple rows of buffer tabs. My coworker, using the
NetBeans Java IDE, always has 4 or 5 rows of buffer tabs below the
editing area. He always uses the mouse to select one of them, and he
seems to remember them by position: they are not sorted in any obvious
order, at least afaict they are not sorted alphabetically. In case he
forgets the position of one of the tabs, he scans all of them
visually. Amazing.
This is fine except I wonder if it would use up too much of the screen
height.
next prev parent reply other threads:[~2003-11-18 23:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 4:09 Two GTK related feature requests Simon Josefsson
2003-10-21 4:17 ` Masatake YAMATO
2003-10-21 4:27 ` Simon Josefsson
2003-10-22 9:25 ` Richard Stallman
2003-10-22 12:04 ` Simon Josefsson
2003-10-22 12:39 ` Luc Teirlinck
2003-10-22 13:44 ` Simon Josefsson
2003-11-02 19:34 ` Jan D.
2003-10-23 2:08 ` Michael Welsh Duggan
2003-10-25 20:08 ` James H.Cloos Jr.
2003-10-26 4:10 ` C-z (Re: Two GTK related feature requests) Karl Eichwalder
2003-10-26 6:11 ` Eli Zaretskii
2003-10-26 8:01 ` Karl Eichwalder
2003-10-27 7:02 ` Richard Stallman
2003-10-27 12:22 ` Kim F. Storm
2003-10-27 12:46 ` Robert J. Chassell
2003-10-27 14:05 ` Kim F. Storm
2003-10-27 18:08 ` Karl Eichwalder
2003-10-27 22:16 ` Robert J. Chassell
2003-10-27 15:47 ` C-z Werner LEMBERG
2003-10-27 16:36 ` C-z (Re: Two GTK related feature requests) Juri Linkov
2003-10-27 19:44 ` Kevin Rodgers
2003-10-28 20:39 ` Richard Stallman
2003-10-29 7:01 ` Karl Eichwalder
2003-10-29 7:28 ` Miles Bader
2003-10-30 4:19 ` Richard Stallman
2003-10-29 9:43 ` David Kastrup
2003-10-29 13:30 ` Stefan Monnier
2003-10-29 14:03 ` Eli Zaretskii
2003-10-29 16:00 ` Luc Teirlinck
2003-10-26 19:01 ` Stefan Monnier
2003-10-26 21:06 ` Miles Bader
2003-10-27 5:50 ` Eli Zaretskii
2003-10-27 6:46 ` Miles Bader
2003-10-27 16:55 ` Juri Linkov
2003-10-28 2:01 ` Miles Bader
2003-10-29 14:15 ` Stephan Stahl
2003-10-29 15:29 ` David Kastrup
2003-11-17 20:40 ` Two GTK related feature requests Kai Grossjohann
2003-11-18 23:03 ` Richard Stallman [this message]
2003-11-19 21:43 ` tabs proposal Alex Schroeder
2003-11-21 4:08 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-10-21 7:34 Two GTK related feature requests David PONCE
2003-10-22 12:43 Robert J. Chassell
2003-10-22 13:59 ` Simon Josefsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1AMEt4-0000Bf-Va@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.