unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: nickrob@snap.net.nz, eliz@gnu.org, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, miles@gnu.org
Subject: Re: Tabbed buffers
Date: Mon, 28 Jan 2008 16:32:37 -0500	[thread overview]
Message-ID: <E1JJban-0003WI-7h@fencepost.gnu.org> (raw)
In-Reply-To: <87myqq5p2o.fsf@uwakimon.sk.tsukuba.ac.jp> (stephen@xemacs.org)

     >     All I was pointing out was that if we introduce frame-level
     >     tabs, then it might make sense to treat the current
     >     "multiple-frames on a single tty" as tabs rather than as
     >     frames.
     > 
     > That seems like an unnecessary complication with no benefit.

    The benefit is that the tabs provide a visual cue (which many users
    will have experience with) of what alternatives are available via
    `next-tab' or `pop-to-tab'.

That benefit comes from having the feature of tabs.
I think it is a good idea to add that feature.

But you are talking about something else: to treat the current
"multiple-frames on a single tty" as tabs rather than as frames.  That
has nothing to do with the benefits tabs provide, and I don't see how
it would provide any benefit.  It would just create an unnecessary
loss of parallelism between the tty case and the graphical display
case, right?

Perhaps you should state your proposal more concretely and precisely.

  parent reply	other threads:[~2008-01-28 21:32 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 21:57 Tabbed buffers Nick Roberts
2008-01-25 22:40 ` Miles Bader
2008-01-25 23:41   ` Nick Roberts
2008-01-26  0:07     ` Miles Bader
2008-01-26  2:47       ` Stefan Monnier
2008-01-26  5:03         ` Miles Bader
2008-01-26  7:24           ` Thomas Lord
2008-01-26 19:07           ` Stefan Monnier
2008-01-26 14:38         ` Chong Yidong
2008-01-27  0:44           ` Richard Stallman
2008-01-27  1:21             ` Miles Bader
2008-01-27  1:41               ` Stefan Monnier
2008-01-27 16:04                 ` Richard Stallman
2008-01-27  1:50               ` Nick Roberts
2008-01-27  1:58                 ` Miles Bader
2008-01-27  2:10                   ` Nick Roberts
2008-01-27  0:45         ` Richard Stallman
2008-01-27  4:09           ` Eli Zaretskii
2008-01-27 16:13             ` T. V. Raman
2008-01-27 20:59               ` Stefan Monnier
2008-01-27 20:59             ` Stefan Monnier
2008-01-27 23:31               ` Robert J. Chassell
2008-01-28  2:08                 ` Stefan Monnier
2008-01-28  7:17               ` Richard Stallman
2008-01-28  8:31                 ` Stephen J. Turnbull
2008-01-28 15:17                   ` Stefan Monnier
2008-01-28 17:22                     ` Stephen J. Turnbull
2008-01-28 18:18                       ` Stefan Monnier
2008-01-28 19:18                         ` Stephen J. Turnbull
2008-01-28 21:30                           ` Nick Roberts
2008-01-29  6:53                             ` Stephen J. Turnbull
2008-01-29  7:19                               ` Nick Roberts
2008-01-29  8:08                                 ` Stephen J. Turnbull
2008-01-28 21:32                     ` Richard Stallman
2008-01-28 23:05                       ` Bastien Guerry
2008-01-30  6:16                         ` Richard Stallman
2008-01-30  7:53                           ` Bastien Guerry
2008-01-28 21:32                   ` Richard Stallman [this message]
2008-01-29  7:10                     ` Stephen J. Turnbull
2008-01-30  6:16                       ` Richard Stallman
2008-02-01  3:50               ` T. V. Raman
2008-02-01 18:26                 ` Richard Stallman
2008-02-03  2:06                   ` T. V. Raman
2008-02-03 16:18                     ` Richard Stallman
2008-01-27 19:55           ` Using several frames on TTYs, switching them, terminology: [Is also: Tabbed buffers] Alan Mackenzie
2008-01-27 20:52             ` Eli Zaretskii
2008-01-27 21:33               ` Alan Mackenzie
2008-01-28  4:15                 ` Eli Zaretskii
2008-02-01  3:32               ` T. V. Raman
2008-01-27 21:13             ` Stefan Monnier
2008-01-27 21:50               ` Alan Mackenzie
2008-01-28  2:03                 ` Stefan Monnier
2008-01-28  7:17             ` Richard Stallman
2008-01-28 15:42               ` David De La Harpe Golden
2008-01-28 21:32                 ` Richard Stallman
2008-01-26  9:14   ` Tabbed buffers Eli Zaretskii
2008-01-26 11:36     ` Robert J. Chassell
2008-01-26  9:10 ` Eli Zaretskii
2008-01-27  0:12   ` Nick Roberts
2008-01-27  4:07     ` Eli Zaretskii
2008-01-27  4:48       ` Nick Roberts
2008-01-27  8:05         ` Is there any document about Emacs implementation (C source code)? brianjiang
2008-01-27  9:40           ` dhruva
2008-01-27 20:32             ` Stephen J. Turnbull
2008-01-27 20:57               ` Eli Zaretskii
2008-01-27 17:18         ` Tabbed buffers Eli Zaretskii

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=E1JJban-0003WI-7h@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=nickrob@snap.net.nz \
    --cc=stephen@xemacs.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 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).