From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Tabs are ready? -> Let us give a definition of tabs. Date: Mon, 06 Feb 2012 18:05:09 +0100 Message-ID: <4F300845.1090709@gmx.at> References: <4F2E5D33.6020406@gmx.at> <4F2E8185.4080706@gmx.at> <4F2EC768.4050603@gmx.at> <4F2FAD31.9040702@gmx.at> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1328547932 28273 80.91.229.3 (6 Feb 2012 17:05:32 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 6 Feb 2012 17:05:32 +0000 (UTC) Cc: Juri Linkov , Emacs Dev To: Alin Soare Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 06 18:05:31 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RuS0N-0000zr-Nx for ged-emacs-devel@m.gmane.org; Mon, 06 Feb 2012 18:05:28 +0100 Original-Received: from localhost ([::1]:59121 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RuS0N-0003VC-5p for ged-emacs-devel@m.gmane.org; Mon, 06 Feb 2012 12:05:27 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:43716) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RuS0D-0003Uj-1y for emacs-devel@gnu.org; Mon, 06 Feb 2012 12:05:24 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RuS08-0001hQ-L5 for emacs-devel@gnu.org; Mon, 06 Feb 2012 12:05:16 -0500 Original-Received: from mailout-de.gmx.net ([213.165.64.23]:32912) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RuS08-0001hG-AO for emacs-devel@gnu.org; Mon, 06 Feb 2012 12:05:12 -0500 Original-Received: (qmail invoked by alias); 06 Feb 2012 17:05:11 -0000 Original-Received: from 62-47-36-152.adsl.highway.telekom.at (EHLO [62.47.36.152]) [62.47.36.152] by mail.gmx.net (mp031) with SMTP; 06 Feb 2012 18:05:11 +0100 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1+54Dl+Eia5dL7im6rHPoR4lwZrCLWnm8jUK0TreV Cn0O3Hh2LugL5M In-Reply-To: X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 213.165.64.23 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:148275 Archived-At: >> How do you communicate to the tab what the "something" is? > > > > execute 'grep -i foo *' in background , example I didn't ask "what" the something is. I asked "how" you want to communicate that something to the tab. >>> 2. The 'show event should commute to the buffer *grep* >> This is the standard buffer switching functionality. >> >> > I know how to commute a buffer. In this case of tab, I want the show event > to commute to a given buffer. I meant that this is the standard behavior associated with tabs: Display something like a file or a webpage in the display area associated with the tab. >>> 3. when grep finds something, and the tab is hidden , the tab widget to >>> change the color >> What sense does it make to have a hidden tab change color? And what >> kind of event is this in your nomenclature? >> >> > Tabs should register a callback for an event , for example, when i/o > arrives in the given process... But what do you want to do? I suppose you want to show the tab that was hidden before. OTOH "show" in your nomenclature meant something different so far: Do some standard action associated with the tab like switching buffers or restoring a window configuration. >>> 4. The 'close event should kill the *grep* buffer, and the process , if >> it >>> had not finished yet >>> Could you do this using buttons in toolbar or menubar, as you insist ? >> So far I'd only insist that saving and restoring window configurations >> should be done with the menubar rather than with a tab. I never ever >> use toolbars but I think that mail handling routines using the toolbar >> (could) do such things routinely (inform of new mail, kill a buffer and >> remove the associated button when mail has been sent , ...). >> >> > Why do you change the subject of discussion ? saving and restoring window > configurations concerns other type of tab, not this one I am talking here. I referred to the window configuration example because so far that was the only one where I "insisted" on providing a menubar entry rather than a tab. You can't accuse me of insistence with an example you didn't provide before. My argument was that the "'close event" for the *grep* buffer is rather similar to a toolbar button provided by an email problem which, when hit, causes the currently written mail to get sent and the associated display area where that mail was shown removed. I don't know of any MUA that uses tabs for such a purpose but I don't want to exclude it. I also agree that the hourglass functionality of a tab you cited earlier (that is changing the color of a tab while work like grep searching is in progress) can be useful, for example, when performing a couple of grep searches or compilations simultaneously. martin