unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: Two GTK related feature requests
Date: Wed, 22 Oct 2003 12:43:43 +0000 (UTC)	[thread overview]
Message-ID: <m1ACIL1-000UNVC@rattlesnake.com> (raw)

    * "Tabbed editing".  People using modern web browsers will know what I
      mean.  It is very addictive.  Essentially it would add buttons at
      the top of the Emacs window, one button for each buffer.  Clicking
      on one button will change focus to that buffer.  ...

To try this out, I am using tabbar.el from

    http://unc.dl.sourceforge.net/sourceforge/emhacks/tabbar-1.3.tar.gz

The user interface created by tabbar.el does not scale.

Right now I have 41 open buffers, which is fewer than usual.  To see
the various groups of files, I need a window width of 125 characters

To see the file names in just the `text' group, I need a window that
is 147 characters wide.  My normal window width is the conventional 80
characters.

The `tabbed editing' notion is interesting but I am not sure that any
of the obvious solutions work in the long run.  For example, one could
fill the tab line when needed, so that characters to the right of the
fill-column are moved down to another line.  But this suggestion uses
up screen real estate.

Newbies will say that they never keep more than a dozen buffers open
at once and that the current method will work for them -- but it is
awkward to design features that work for newbies and fail as the
newbies become more expert.

A vertical list is a possibility.  That is what `list-buffers'
provides, as does clicking on the `Buffers' item in the menu bar.

Unfortunately, even now, with only 41 open buffers, my menu bar
`Buffers' list runs out the bottom of the screen (it has a little
arrow at the bottom) -- this makes this feature less convenient than
the buffer list provided by buff-menu.el.

In windows, such as X, perhaps the names could be put in another
frame, like speedbar does.  However, speedbar does not scale well
either -- not for my directories -- but might work on a `tabbed'
buffer list, since the number of open buffers is likely to be smaller
than the number of files in a directory.  (For example, in one
directory right now I have 2361 personal `how-to-*' files, including
backups, but as I said, only 41 open buffers.)  Because it does not
scale, I do not use speedbar; consequently, I do not know the
advantages or disadvantages of this possibility.

--
    Robert J. Chassell                         Rattlesnake Enterprises
    http://www.rattlesnake.com                  GnuPG Key ID: 004B4AC8
    http://www.teak.cc                             bob@rattlesnake.com

             reply	other threads:[~2003-10-22 12:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 12:43 Robert J. Chassell [this message]
2003-10-22 13:59 ` Two GTK related feature requests Simon Josefsson
  -- strict thread matches above, loose matches on Subject: below --
2003-10-21  7:34 David PONCE
2003-10-21  4:09 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-11-17 20:40   ` Kai Grossjohann
2003-11-18 23:03     ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1ACIL1-000UNVC@rattlesnake.com \
    --to=bob@rattlesnake.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).