From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#36610: [PATCH] Make finder-exit use quit-window Date: Fri, 12 Jul 2019 10:57:28 +0300 Message-ID: <83pnmf3ct3.fsf@gnu.org> References: <83y3133gnf.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="140457"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 36610@debbugs.gnu.org To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jul 12 09:58:08 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hlqRT-000aPL-5r for geb-bug-gnu-emacs@m.gmane.org; Fri, 12 Jul 2019 09:58:07 +0200 Original-Received: from localhost ([::1]:47342 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hlqRS-0000lC-5E for geb-bug-gnu-emacs@m.gmane.org; Fri, 12 Jul 2019 03:58:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45480) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hlqRP-0000k7-2n for bug-gnu-emacs@gnu.org; Fri, 12 Jul 2019 03:58:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hlqRO-0004fO-6Q for bug-gnu-emacs@gnu.org; Fri, 12 Jul 2019 03:58:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58634) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hlqRN-0004f4-QY for bug-gnu-emacs@gnu.org; Fri, 12 Jul 2019 03:58:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hlqRN-0004eJ-MH for bug-gnu-emacs@gnu.org; Fri, 12 Jul 2019 03:58:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 12 Jul 2019 07:58:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 36610 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 36610-submit@debbugs.gnu.org id=B36610.156291826717842 (code B ref 36610); Fri, 12 Jul 2019 07:58:01 +0000 Original-Received: (at 36610) by debbugs.gnu.org; 12 Jul 2019 07:57:47 +0000 Original-Received: from localhost ([127.0.0.1]:39221 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hlqR9-0004di-60 for submit@debbugs.gnu.org; Fri, 12 Jul 2019 03:57:47 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:33055) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hlqR8-0004dW-7I for 36610@debbugs.gnu.org; Fri, 12 Jul 2019 03:57:46 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51365) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hlqR0-0004HK-4F; Fri, 12 Jul 2019 03:57:38 -0400 Original-Received: from [176.228.60.248] (port=3772 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hlqQy-0003XT-QU; Fri, 12 Jul 2019 03:57:37 -0400 In-reply-to: (message from Stefan Kangas on Fri, 12 Jul 2019 09:20:02 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:162755 Archived-At: > From: Stefan Kangas > Date: Fri, 12 Jul 2019 09:20:02 +0200 > Cc: 36610@debbugs.gnu.org > > Does the above clear it up sufficiently? Yes, thanks. Please try in the future including such details either in the bug report, or in the commit log message, or in the comments to the changes, whatever is appropriate for the case at hand.