From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: Working with one buffer in two frames/windows Date: Sun, 13 Jul 2008 13:06:06 +0000 Message-ID: <20080713130606.GA1076@muc.de> References: <86tzew3d1c.fsf@lola.quinscape.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1215952850 3202 80.91.229.12 (13 Jul 2008 12:40:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 13 Jul 2008 12:40:50 +0000 (UTC) Cc: emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 13 14:41:38 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 1KI0tV-0006g6-OW for ged-emacs-devel@m.gmane.org; Sun, 13 Jul 2008 14:41:38 +0200 Original-Received: from localhost ([127.0.0.1]:46370 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KI0sd-0000oM-Qd for ged-emacs-devel@m.gmane.org; Sun, 13 Jul 2008 08:40:43 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KI0sY-0000oH-K6 for emacs-devel@gnu.org; Sun, 13 Jul 2008 08:40:38 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KI0sW-0000nb-L3 for emacs-devel@gnu.org; Sun, 13 Jul 2008 08:40:37 -0400 Original-Received: from [199.232.76.173] (port=59748 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KI0sW-0000nY-Hj for emacs-devel@gnu.org; Sun, 13 Jul 2008 08:40:36 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:4703 helo=mail.muc.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KI0sW-0003Ft-Ov for emacs-devel@gnu.org; Sun, 13 Jul 2008 08:40:37 -0400 Original-Received: (qmail 23657 invoked by uid 3782); 13 Jul 2008 12:40:29 -0000 Original-Received: from acm.muc.de (pD9E528FE.dip.t-dialin.net [217.229.40.254]) by colin2.muc.de (tmda-ofmipd) with ESMTP; Sun, 13 Jul 2008 14:40:27 +0200 Original-Received: (qmail 2134 invoked by uid 1000); 13 Jul 2008 13:06:06 -0000 Content-Disposition: inline In-Reply-To: <86tzew3d1c.fsf@lola.quinscape.zz> User-Agent: Mutt/1.5.9i X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) X-Primary-Address: acm@muc.de X-detected-kernel: by monty-python.gnu.org: FreeBSD 4.6-4.9 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:100638 Archived-At: Hi, David and everybody else, On Fri, Jul 11, 2008 at 12:55:59PM +0200, David Kastrup wrote: > Hi, > it is annoyingly impossible to keep working with two views of the same > buffer. For example, say that I have a file text.tex open in two frames > since I want to work on two different locations of it via > comparison/cut&paste/whatever. Just a slight clarification: the problems are as bad with two views of a file in two windows within one frame. > Now I type M-x gnus RET, read news and quit again. As a consequence, a > totally unrelated buffer pops up. And of course, when I get back the > buffer again (which is not the default offered), the window point is > lost and replaced by that of the other frame that is still on. > That is quite a nuisance. I disagree somewhat on this point. It is an enormous pain in the cdr, not "quite a nuisance". > Are there some ways to make a two-view setup less ephemeral? I'd like to throw the following idea into the ring for discussion: Change the 'buffer-list' frame parameter (page "Buffer Parameters" in the elisp manual) from: `buffer-list' A list of buffers that have been selected in this frame, ordered most-recently-selected first. to: `buffer-list' A list of information about buffers that have been selected in this frame, ordered most-recently-selected first. There is one entry for each buffer, which looks like this: (BUFFER, POINT, .....) , where "...." needs to be thought about. Possibly it could contain details of the window size, and where in the window point is. This information would then be used by C-x k, C-x 4 b, and the like. > David Kastrup -- Alan Mackenzie (Nuremberg, Germany).