unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: David De La Harpe Golden <david@harpegolden.net>
Cc: "alin.s" <alinsoar@voila.fr>, emacs-devel@gnu.org
Subject: Tabs (was: Next pretest)
Date: Mon, 25 Jan 2010 11:12:32 +0200	[thread overview]
Message-ID: <87sk9uo8e7.fsf_-_@mail.jurta.org> (raw)
In-Reply-To: <4B5C76B2.5080702@harpegolden.net> (David De La Harpe Golden's message of "Sun, 24 Jan 2010 16:34:58 +0000")

>> Tabs are also ready. For the console it's completely finished; for GTK I
>> have to make the latests modifications. For Lesstif and Athena I just found
>> some notebook widgets, and have to learn how to use them.
>
> Um. What sort of tabs?  Last time I tuned in (some time ago), people had
> very different ideas about how tabs should work.
>
> For my part, I presently have a half-formed notion they should be another
> dimension for emacs window splitting along with horizontal and vertical,
> and therefore an aspect of window configurations.  Notably, I don't have
> any working code though.

This is one of possible tab uses that requires window grouping functionality
and can help to implement Eclipse-like perspectives.

> Another option which I looked into at one stage was toplevel-only tabs that
> collected and switched between whole emacs frames. i.e. tabs "outside"
> frames.  The gtk+ notebook container widget model was particular suitable
> for that approach IIRC, as it was sort of emulating a tabbed window manager
> internal to gtk+, and gave you drag-drop and rearrangement for "free", but
> I eventually thought the window splitting model was more emacsy
> and general.

Such toplevel tabs are useful to implement webbrowser-like tabs
switching frames or window configurations.

> The one thing I really don't like is the idea of tabs-as-list-of-buffers -
> simply doesn't scale well to even my typical open buffer count (10s rather
> than 100s.), and is a waste of what could be a more versatile ui feature
> for the likes of IDE-type modes.

tabbar.el successfully implements the idea of using the tabbar
to switch buffers.

-- 
Juri Linkov
http://www.jurta.org/emacs/




  parent reply	other threads:[~2010-01-25  9:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 14:46 Next pretest Chong Yidong
2010-01-24 15:31 ` alin.s
2010-01-24 16:34   ` David De La Harpe Golden
2010-01-24 16:47     ` David De La Harpe Golden
2010-01-24 19:44     ` Chad Brown
2010-01-24 21:22       ` Chong Yidong
2010-01-27 20:34         ` alin.s
2010-01-25  9:12     ` Juri Linkov [this message]
2010-01-25 16:49     ` Lluís
2010-01-25 23:13 ` Juanma Barranquero
2010-01-26 15:28   ` Chong Yidong
2010-01-26 15:46     ` Juanma Barranquero
2010-01-26 18:09       ` Eli Zaretskii
2010-01-26 18:27         ` Juanma Barranquero
2010-01-26 23:13           ` Juanma Barranquero
2010-01-26 23:48         ` Juanma Barranquero
2010-01-27  2:02           ` Jason Rumney
2010-01-27  9:50             ` Juanma Barranquero
2010-01-27 14:03               ` Jason Rumney
2010-01-27 16:06                 ` Juanma Barranquero
2010-01-27 16:18                   ` Jason Rumney
2010-01-27 20:07                     ` Juanma Barranquero
2010-01-27 20:32                       ` Chong Yidong
2010-01-29 12:14                     ` Eli Zaretskii
2010-01-29 12:38                       ` Juanma Barranquero

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=87sk9uo8e7.fsf_-_@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=alinsoar@voila.fr \
    --cc=david@harpegolden.net \
    --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 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).