From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Tab bar Date: Tue, 08 Apr 2008 02:27:33 +0300 Organization: JURTA Message-ID: <87r6dhbbd6.fsf@jurta.org> References: <87wsnaso3h.fsf@jurta.org> <87d4p2tuim.fsf@jurta.org> <87prt2qzbd.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1207612013 30127 80.91.229.12 (7 Apr 2008 23:46:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Apr 2008 23:46:53 +0000 (UTC) Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 08 01:47:25 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 1Jj13d-0004mD-Ex for ged-emacs-devel@m.gmane.org; Tue, 08 Apr 2008 01:47:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jj130-0002Wp-Cl for ged-emacs-devel@m.gmane.org; Mon, 07 Apr 2008 19:46:46 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jj10m-0008Nz-I0 for emacs-devel@gnu.org; Mon, 07 Apr 2008 19:44:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jj10h-0008LZ-Jn for emacs-devel@gnu.org; Mon, 07 Apr 2008 19:44:27 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jj10h-0008LL-2X for emacs-devel@gnu.org; Mon, 07 Apr 2008 19:44:23 -0400 Original-Received: from relay01.kiev.sovam.com ([62.64.120.200]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jj10d-0001dL-5q; Mon, 07 Apr 2008 19:44:19 -0400 Original-Received: from [83.170.232.243] (helo=smtp.svitonline.com) by relay01.kiev.sovam.com with esmtp (Exim 4.67) (envelope-from ) id 1Jj10Z-000OYD-FN; Tue, 08 Apr 2008 02:44:16 +0300 In-Reply-To: (Richard Stallman's message of "Mon, 07 Apr 2008 10:59:31 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (x86_64-pc-linux-gnu) X-Scanner-Signature: 1e897a521fdb5eac39b1f944f187ca57 X-DrWeb-checked: yes X-SpamTest-Envelope-From: juri@jurta.org X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Not Detected X-SpamTest-Info: Profiles 2574 [Apr 07 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {HEADERS: header Content-Type found without required header Content-Transfer-Encoding} X-SpamTest-Method: none X-SpamTest-Rate: 10 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release X-detected-kernel: by monty-python.gnu.org: FreeBSD 4.8-5.1 (or MacOS X 10.2-10.3) 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:94648 Archived-At: > Just as web browsers provide an option to choose between opening pages > in a new tab or in the same tab, and similarly to the Emacs option > `pop-up-frames', we could create a new user option `pop-up-tabs' whose > non-nil value will always display a new buffer in a new tab, and we > could even set it to non-nil by default for the convenience of new users. > > This idea makes no sense to me. Is this because you don't use web browsers? In most modern web browsers a tab displays a web page, but the same tab can switch between different web pages (so web pages are equivalent to Emacs buffers). When the user wants to visit a new page, then depending on such option, the browser can either open it in the same tab or create a new tab. Often this preference can't be defined in advance, so there are special keys to choose between these options, e.g. simply clicking on a link opens a web page in the same tab, but opens it in a new tab. > If the default usage of the tab bar is to switch buffers in the > selected window, then every new buffer will inevitably get a "new tab" > regardless of how it is displayed. So what question are you > talking about? Of course, selecting a tab to switch buffers should not create a new tab (internally this can be implemented using functions like `switch-to-buffer' that don't create a new window or a new tab), but if the user invokes a command that calls `display-buffer' then a new option `pop-up-tabs' makes sense to allow displaying it in a new tab just as `pop-up-frames' allows displaying it in a new frame. -- Juri Linkov http://www.jurta.org/emacs/