From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: pjb@informatimago.com (Pascal J. Bourguignon) Newsgroups: gmane.emacs.help Subject: Re: Using only one emacs session Date: Sun, 17 May 2009 01:05:01 +0200 Organization: Informatimago Message-ID: <87tz3k644i.fsf@galatea.local> References: <32aa9d73-5926-4435-8b76-646c53a58fd0@e20g2000vbc.googlegroups.com> <87eiup8353.fsf@galatea.local> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1242517250 32527 80.91.229.12 (16 May 2009 23:40:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 16 May 2009 23:40:50 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun May 17 01:40:44 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1M5TUh-0001Mc-80 for geh-help-gnu-emacs@m.gmane.org; Sun, 17 May 2009 01:40:43 +0200 Original-Received: from localhost ([127.0.0.1]:42140 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M5TUg-00032L-Oh for geh-help-gnu-emacs@m.gmane.org; Sat, 16 May 2009 19:40:42 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!goblin2!goblin.stu.neva.ru!ecngs!feeder2.ecngs.de!proxad.net!feeder1-1.proxad.net!cleanfeed4-a.proxad.net!nnrp10-2.free.fr!not-for-mail Original-Newsgroups: gnu.emacs.help Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en X-Disabled: X-No-Archive: no User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/22.3 (darwin) Cancel-Lock: sha1:MTk3OTZiZTQzNTRiYmNkODMzN2JlMGJjYTJhYzhkODE2YzY2ZmJkNQ== Original-Lines: 61 Original-NNTP-Posting-Date: 17 May 2009 01:05:02 MEST Original-NNTP-Posting-Host: 88.182.134.169 Original-X-Trace: 1242515102 news-2.free.fr 11289 88.182.134.169:60711 Original-X-Complaints-To: abuse@proxad.net Original-Xref: news.stanford.edu gnu.emacs.help:169248 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:64505 Archived-At: Francis Moreau writes: > On May 16, 5:43 pm, p...@informatimago.com (Pascal J. Bourguignon) > wrote: >> Francis Moreau writes: >> > yes, that's one possibility I did evaluate. But the main concern is >> > that I don't know how to get a list of all registers with a >> > description for each. >> >> Then why don't you ask emacs how to get a list of all registers with a >> description for each? >> > > Well the result is quite bad: > > Register a contains a window configuration. > Register b contains a window configuration. > Register c contains a window configuration. > > which is not very useful IMHO. The results are better for other kinds of register contents. But if you're not happy with this result, why don't you patch it? The problem here is that window-configuration are opaque objects. We have about only three functions: (current-window-configuration) to get the current window configuration (set-window-configuration wc) to set the window configuration and (compare-window-configuration wc1 wc2) to compare them. and these functions are implemented in C. You have two solutions: If you want to have accessors to get details about eg. the windows in a given window configuration, you would have to patch the C code of emacs. Untasty, but it would probably be the best solution. An alternative would be to put an advice on window-configuration-to-register. This advice would collect whatever information about the current window configuration you may like to report in the register list, (eg. a list of the displayed buffer names), and associate it to the window-configuration so it can be displayed by list-register. > Other things (perharps more important) that make window package > superior is that it allows me to use some window navigation 'a la' gnu > screen (go back and forth between the 2 most recent visited windows, > go to the next/previous window, select a window among a list of well > described window etc...). I don't know what "window package" is, so I cannot comment, but it seems to me that these features are already present in emacs, or easily added. -- __Pascal Bourguignon__