From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Bastien Newsgroups: gmane.emacs.devel Subject: Re: Neat features in Eclipse editor Date: Tue, 25 Mar 2008 02:06:03 +0100 Message-ID: <87iqzb1ukk.fsf@bzg.ath.cx> References: <873aqia0eh.fsf@stupidchicken.com> <873aqiw4xm.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 1206407182 31376 80.91.229.12 (25 Mar 2008 01:06:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 25 Mar 2008 01:06:22 +0000 (UTC) Cc: rms@gnu.org, emacs-devel To: joakim@verona.se Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 25 02:06:52 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 1Jdxco-00069s-Qv for ged-emacs-devel@m.gmane.org; Tue, 25 Mar 2008 02:06:51 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JdxcD-0005gy-Am for ged-emacs-devel@m.gmane.org; Mon, 24 Mar 2008 21:06:13 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JdxcA-0005gs-DN for emacs-devel@gnu.org; Mon, 24 Mar 2008 21:06:10 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jdxc8-0005gg-Ur for emacs-devel@gnu.org; Mon, 24 Mar 2008 21:06:10 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jdxc8-0005gd-JF for emacs-devel@gnu.org; Mon, 24 Mar 2008 21:06:08 -0400 Original-Received: from fk-out-0910.google.com ([209.85.128.187]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jdxc8-0002g7-2t for emacs-devel@gnu.org; Mon, 24 Mar 2008 21:06:08 -0400 Original-Received: by fk-out-0910.google.com with SMTP id 26so3632423fkx.10 for ; Mon, 24 Mar 2008 18:06:06 -0700 (PDT) Original-Received: by 10.78.172.5 with SMTP id u5mr23188894hue.10.1206407166739; Mon, 24 Mar 2008 18:06:06 -0700 (PDT) Original-Received: from bzg.ath.cx ( [78.114.246.77]) by mx.google.com with ESMTPS id j2sm30007384mue.3.2008.03.24.18.06.04 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 24 Mar 2008 18:06:05 -0700 (PDT) Original-Received: by bzg.ath.cx (Postfix, from userid 1000) id 7F458157978; Tue, 25 Mar 2008 02:06:03 +0100 (CET) In-Reply-To: (joakim@verona.se's message of "Mon, 24 Mar 2008 20:02:25 +0100") User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) 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:93366 Archived-At: joakim@verona.se writes: > Sub-frames are not like windows, they are like frames, because they > contain windows and are not affected by what happens in other frames. (Maybe using "workspace" instead of "sub-frames" might help clarifying things a bit.) > Tabs are usually complementary to the feature I try describe. The first time I talked about "workspaces" was when I tried to explain my use of tabs with elscreen: http://article.gmane.org/gmane.emacs.devel/87765 Sorry for the self-quote, but it sounds like ideas there can help describe a workspace from yet another perspective: ,----[ http://article.gmane.org/gmane.emacs.devel/87765 ] | It seems to me that, in this discussion, we should really talk about | "workspaces" - not "tabs". Or at least we could disambiguate these and | use "tab" for the visual UI feature and "workspace" for the underlying | window configuration (and the properties we would like to attach to it.) | | I use elscreen to easily *cycle* through workspaces and to easily | *create* new ones. | | Having "workspaces" (or whatever you want to call them) would be very | useful for letting variables be local to them. For example I use this: | | (make-variable-buffer-local 'search-ring) | | but this would make more sense in a workspace rather than in a buffer. | | Or see the function `erc-iswitchb': it restricts the list of buffers to | the one that are used by ERC. I've implemented something like this for | Org as well. If you use ERC in a dedicated workspace, then the notion | of "ERC buffers" is really an instance of the more general notion of | "This workspace buffers." `---- -- Bastien