unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: nickrob@snap.net.nz, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: Tabbed buffers
Date: Sat, 26 Jan 2008 19:45:31 -0500	[thread overview]
Message-ID: <E1JIveN-00008W-5p@fencepost.gnu.org> (raw)
In-Reply-To: <jwvprvpi9v9.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 25 Jan 2008 21:47:48 -0500)

      So the behavior of display-buffer could be configured to
    either use the current window, or pop a new window, or pop a new tab or
    pop a new frame.

When a window has multiple tabs, only one of them is displayed at a time.
For most purposes, the non-current tabs can be ignored.
However, for purposes of displaying a buffer, switching tabs
could be one method `display-buffer' can use.

    For what it's worth, I think that if we introduce this notion of tab, we
    should change ttys to use tabs rather than frames since tty frames
    behave much more like tabs.  Of course multiple ttys would each get its
    own frame.

Tabs should be supported on ttys, but we should not get rid of the
current frame support on ttys.  The main reason we have frames on ttys
is to reduce the difference between handling of ttys and handling of
graphics displays.  People normally don't use multiple frames on ttys,
and that is ok, people can continue not to use them.  But getting rid
of them would just mean trouble.

  parent reply	other threads:[~2008-01-27  0:45 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 [this message]
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
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=E1JIveN-00008W-5p@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=nickrob@snap.net.nz \
    /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).