From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thomas Lord Newsgroups: gmane.emacs.devel Subject: Re: Tabbed buffers Date: Fri, 25 Jan 2008 23:24:10 -0800 Message-ID: <479AE01A.80403@emf.net> References: <18330.23354.579245.68671@kahikatea.snap.net.nz> <87ejc5sf4l.fsf@catnip.gol.com> <18330.29609.396872.678539@kahikatea.snap.net.nz> <87wspxqwjv.fsf@catnip.gol.com> <87ir1hqits.fsf@catnip.gol.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1520982410==" X-Trace: ger.gmane.org 1201326597 21968 80.91.229.12 (26 Jan 2008 05:49:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 26 Jan 2008 05:49:57 +0000 (UTC) Cc: Nick Roberts , Stefan Monnier , emacs-devel@gnu.org To: Miles Bader Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 26 06:50:13 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JIdve-00024a-55 for ged-emacs-devel@m.gmane.org; Sat, 26 Jan 2008 06:50:10 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JIdvD-0002dI-B0 for ged-emacs-devel@m.gmane.org; Sat, 26 Jan 2008 00:49:43 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JIdv3-0002cb-Hp for emacs-devel@gnu.org; Sat, 26 Jan 2008 00:49:33 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JIdv2-0002bs-36 for emacs-devel@gnu.org; Sat, 26 Jan 2008 00:49:32 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JIdv1-0002bo-Qb for emacs-devel@gnu.org; Sat, 26 Jan 2008 00:49:31 -0500 Original-Received: from mail.42inc.com ([205.149.0.25]) by monty-python.gnu.org with esmtps (SSL 3.0:RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1JIdux-0004aN-TC; Sat, 26 Jan 2008 00:49:28 -0500 X-TFF-CGPSA-Version: 1.5 X-TFF-CGPSA-Filter-42inc: Scanned X-42-Virus-Scanned: by 42 Antivirus -- Found to be clean. Original-Received: from [69.236.72.159] (account lord@emf.net HELO [192.168.1.64]) by mail.42inc.com (CommuniGate Pro SMTP 5.0.13) with ESMTPA id 20696314; Fri, 25 Jan 2008 21:49:18 -0800 User-Agent: Thunderbird 1.5.0.5 (X11/20060808) In-Reply-To: <87ir1hqits.fsf@catnip.gol.com> X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:87543 Archived-At: This is a multi-part message in MIME format. --===============1520982410== Content-Type: multipart/alternative; boundary="------------060108070601080007080504" This is a multi-part message in MIME format. --------------060108070601080007080504 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Miles Bader wrote: > Stefan Monnier writes: > >> I could imagine introducing tabs as a new concept between windows >> and frames. 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. >> > > Hmm, do we want the tab-bar to be per-frame, or per-emacs-window? > As a user --- my thought is that a "tab" should contain a frame. i.e., it's kind of filling in for a gap left by crappy X11 window managers. Coordination with the GNU desktop project here might help. -t > For "switching buffer" use of tabs, per-emacs-window seems like it might > be more useful, though obviously eating more screen real-estate. > [With such a setup, it would be useful to have "non-tabbed" and "tabbed" > emacs windows though I don't know how that UI would work...] > > -Miles > > --------------060108070601080007080504 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Miles Bader wrote: 
Stefan Monnier <monnier@iro.umontreal.ca> writes:
  
I could imagine introducing tabs as a new concept between windows
and frames.  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.
    

Hmm, do we want the tab-bar to be per-frame, or per-emacs-window?


As a user --- my thought is that a "tab" should contain a frame.
i.e., it's kind of filling in for a gap left by crappy X11 window
managers.


Coordination with the GNU desktop project here might help.

-t





For "switching buffer" use of tabs, per-emacs-window seems like it might
be more useful, though obviously eating more screen real-estate.
[With such a setup, it would be useful to have "non-tabbed" and "tabbed"
emacs windows though I don't know how that UI would work...]

-Miles

--------------060108070601080007080504-- --===============1520982410== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel --===============1520982410==--