From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: managing windows in two frames Date: Wed, 04 Sep 2013 15:33:58 -0400 Message-ID: References: <8561uiclrj.fsf@stephe-leake.org> <5225DB8D.6060709@gmx.at> <858uzcbggs.fsf@stephe-leake.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1378323254 23562 80.91.229.3 (4 Sep 2013 19:34:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 4 Sep 2013 19:34:14 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 04 21:34:17 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VHIqF-0007DN-8G for ged-emacs-devel@m.gmane.org; Wed, 04 Sep 2013 21:34:15 +0200 Original-Received: from localhost ([::1]:54909 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHIqE-0006Fy-QI for ged-emacs-devel@m.gmane.org; Wed, 04 Sep 2013 15:34:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57783) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHIq5-0006Fe-TT for emacs-devel@gnu.org; Wed, 04 Sep 2013 15:34:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VHIq0-0000lm-1B for emacs-devel@gnu.org; Wed, 04 Sep 2013 15:34:05 -0400 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:53754) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VHIpz-0000le-T6 for emacs-devel@gnu.org; Wed, 04 Sep 2013 15:33:59 -0400 Original-Received: from faina.iro.umontreal.ca (lechon.iro.umontreal.ca [132.204.27.242]) by pruche.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id r84JXwqL013546; Wed, 4 Sep 2013 15:33:58 -0400 Original-Received: by faina.iro.umontreal.ca (Postfix, from userid 20848) id 593C5B41C5; Wed, 4 Sep 2013 15:33:58 -0400 (EDT) In-Reply-To: <858uzcbggs.fsf@stephe-leake.org> (Stephen Leake's message of "Wed, 04 Sep 2013 13:16:03 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV4691=0 X-NAI-Spam-Version: 2.3.0.9362 : core <4691> : streams <1031558> : uri <1527068> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.22 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:163190 Archived-At: >> `display-buffer' decisions are currently not based on a prefix argument >> given. > Right; that's new. I find it very convenient. But it's fundamentally broken (the prefix arg is an argument to the command being run, and the relationship between the command being run and the call to `display-buffer' can be arbitrary). IOW it's perfectly fine for personal use but we can't use that in lisp/window.el. >> Maybe we can reconcile your idea with Stefan's proposal to use >> special prefixes for `display-buffer'-based functions. > Searching the emacs-devel archives, I found: > http://lists.gnu.org/archive/html/emacs-devel/2011-09/msg00299.html > http://lists.gnu.org/archive/html/emacs-devel/2011-08/msg00481.html > That doesn't give a very concrete proposal; can provide a better link? Make C-x 5 a prefix key which sets display-buffer-overriding-action for the duration of the next command. So C-x 5 C-x C-f will do the same as what you currently get with C-x 5 f (of course, we'd also preserve a C-x 5 f binding for backward compatibility, and we wouldn't need find-file-other-frame any more, although we'd also have to keep it for backward compatibility). Of course, other such prefixes could be used, such as C-x 4. And as Martin mentions, we'd want one that can say "display in current window". That should be no harder to define than C-x 4 or C-x 5. More generally you could define such a prefix key that lets you specify a particular window to use in the next command. Stefan