From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Sean Whitton Newsgroups: gmane.emacs.bugs Subject: bug#42210: Add -other-window variants of project-prefix-map commands Date: Sun, 05 Jul 2020 13:25:13 -0700 Message-ID: <875zb1hfpy.fsf@iris.silentflame.com> References: <87blkw5cd3.fsf@iris.silentflame.com> <87tuymh4k9.fsf@iris.silentflame.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36048"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dgutov@yandex.ru, juri@linkov.net To: Drew Adams , 42210@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jul 05 22:26:10 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jsBDG-0009GR-Ql for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 05 Jul 2020 22:26:10 +0200 Original-Received: from localhost ([::1]:58352 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jsBDF-0000hL-ET for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 05 Jul 2020 16:26:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47578) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jsBD8-0000hB-2x for bug-gnu-emacs@gnu.org; Sun, 05 Jul 2020 16:26:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49725) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jsBD7-0005f5-QE for bug-gnu-emacs@gnu.org; Sun, 05 Jul 2020 16:26:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jsBD7-0004Zf-Ku for bug-gnu-emacs@gnu.org; Sun, 05 Jul 2020 16:26:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Sean Whitton Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 05 Jul 2020 20:26:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 42210 X-GNU-PR-Package: emacs Original-Received: via spool by 42210-submit@debbugs.gnu.org id=B42210.159398072417532 (code B ref 42210); Sun, 05 Jul 2020 20:26:01 +0000 Original-Received: (at 42210) by debbugs.gnu.org; 5 Jul 2020 20:25:24 +0000 Original-Received: from localhost ([127.0.0.1]:33038 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jsBCW-0004Yh-Iu for submit@debbugs.gnu.org; Sun, 05 Jul 2020 16:25:24 -0400 Original-Received: from out5-smtp.messagingengine.com ([66.111.4.29]:58273) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jsBCS-0004YP-5l for 42210@debbugs.gnu.org; Sun, 05 Jul 2020 16:25:22 -0400 Original-Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 90CF65C0086; Sun, 5 Jul 2020 16:25:14 -0400 (EDT) Original-Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 05 Jul 2020 16:25:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spwhitton.name; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version:content-type; s=fm3; bh=xC/ImioXdAj08VScDAOZxbj57Z k8VjvE6QBU9Vj6Tp0=; b=vf1hiUWkjEspvqFK9QxTS4zcsgpLhnGDpn9QMoTJVW SUeQLppPdz8ET45NzOdlA5h0h69ZoL8XmlOtv32aRja/ej04rYkJYTPWam/3RYxF y+ES+VHJkZUqLqXZs1rYlU5ah4Fy2w/wVdc4SoETVNlrz9SOh6hSBpeFN0tU2DaE oKL+nMMR9x06xxvBBqt+45Syv6IO4QaSjaidGXR7dQQUCUNKEpNFiievoNM4WUEA 3a/YTlXXRwBxPH+1QPNb5xykDkInr2g5U+Zbd/Ld+P4GQDA2oJvdL30V0SXNOkMb 0d4uRx+gUlklq3MjebafNfBNh5UTF2opgi6gd5pwxXcQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=xC/Imi oXdAj08VScDAOZxbj57Zk8VjvE6QBU9Vj6Tp0=; b=Q8jjIPODhilsFZYhqnWlrQ S64P/w9e2cx24i03d+XFQGwnSEk3vfI/blWvw7gE0bX6hOG+aDZWBhLuUxqazk+n lwah4VBh2WtYEFd7AQO71S1NE7zOH4/f7jSnPvOyGB8Kjft3uuIonVIS6hMQ8FN/ 1q8/C/DWgngCOkufRebNNU1GPtnnHcQ8kgQjv6zmRukVHTnbDVRp2RiHtRjRhMSC 1OSeKelJsfg6JIeD6xn1MD+dVhNDkT+QetWNNI2o/R7pWDRJ/tu1CflzuIFld4yZ GRXabh1fuIKBx/AzM0VKXSqASdcUO1RFnHrjBA6G2Shu/FbGPmU656mkEyRIYRIg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedruddugdduhedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufgjfhffkfggtgesthdtredttddttdenucfhrhhomhepufgvrghnucgh hhhithhtohhnuceoshhpfihhihhtthhonhesshhpfihhihhtthhonhdrnhgrmhgvqeenuc ggtffrrghtthgvrhhnpeegtddvheegfffhffdvfeefhffgjefflefhteevffffkeetgfdt jedtiedvtdevheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehsphifhhhithhtohhnsehsphifhhhithhtohhnrdhnrghmvg X-ME-Proxy: In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:182751 Archived-At: Hello, On Sun 05 Jul 2020 at 11:35AM -07, Drew Adams wrote: > 1. I disagree with calling the macro `define-other-window-command'. > > My disagreement is this: Defining an other-window command > should do just that. It should not define a command that > only "prefers" to display in another window. It should > define a command that actually displays in another window. > > And your doc string in fact says the latter, though the > behavior is, I guess, only the former. Please consider > renaming the macro and fixing the doc string, to make clear > that it's NOT other-window but only maybe-other-window. Hmm, but doesn't pop-to-buffer-other-window also only prefer to use another window, and ultimately defers to the display-buffer-alist machinery? > 2. Why "resultant buffer". What does the buffer result > from? It's about whatever FUNCTION displays, no? Please feel free to suggest alternative phrasing that will be short enough to fit in one line, which I understand to be required. > 3. Presumably FUNCTION must be a _command_. If so, > the arg should be called COMMAND, and the doc adjusted > accordingly. No, it can just be a function too. -- Sean Whitton