From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#32607: 27.0.50; pop-to-buffer in next-error-no-select Date: Fri, 07 Sep 2018 09:28:35 +0200 Message-ID: <5B9228A3.4020700@gmx.at> References: <87a7p0alxv.fsf@mail.linkov.net> <5B8B8DCE.4070704@gmx.at> <87efebjzbd.fsf@mail.linkov.net> <5B8CE360.5030700@gmx.at> <877ek2tdqx.fsf@mail.linkov.net> <5B8E3998.3050907@gmx.at> <87o9ddc8yc.fsf@mail.linkov.net> <5B8F8A1B.3030807@gmx.at> <8736unzjit.fsf@mail.linkov.net> <5B90D17D.5080605@gmx.at> <87efe6iaws.fsf@mail.linkov.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1536305226 32015 195.159.176.226 (7 Sep 2018 07:27:06 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 7 Sep 2018 07:27:06 +0000 (UTC) Cc: 32607@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Sep 07 09:27:02 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fyBAU-0008FC-9M for geb-bug-gnu-emacs@m.gmane.org; Fri, 07 Sep 2018 09:27:02 +0200 Original-Received: from localhost ([::1]:37086 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fyBCZ-0004xy-NN for geb-bug-gnu-emacs@m.gmane.org; Fri, 07 Sep 2018 03:29:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45092) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fyBCU-0004xq-8T for bug-gnu-emacs@gnu.org; Fri, 07 Sep 2018 03:29:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fyBCQ-0002Rx-Ud for bug-gnu-emacs@gnu.org; Fri, 07 Sep 2018 03:29:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:43693) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fyBCQ-0002Rq-Ph for bug-gnu-emacs@gnu.org; Fri, 07 Sep 2018 03:29:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fyBCQ-0001NY-Hv for bug-gnu-emacs@gnu.org; Fri, 07 Sep 2018 03:29:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 07 Sep 2018 07:29:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32607 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32607-submit@debbugs.gnu.org id=B32607.15363053385286 (code B ref 32607); Fri, 07 Sep 2018 07:29:02 +0000 Original-Received: (at 32607) by debbugs.gnu.org; 7 Sep 2018 07:28:58 +0000 Original-Received: from localhost ([127.0.0.1]:48711 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fyBCM-0001NC-1y for submit@debbugs.gnu.org; Fri, 07 Sep 2018 03:28:58 -0400 Original-Received: from mout.gmx.net ([212.227.15.19]:55283) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fyBCK-0001Mx-6n for 32607@debbugs.gnu.org; Fri, 07 Sep 2018 03:28:56 -0400 Original-Received: from [192.168.1.101] ([212.95.5.234]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MN1j6-1fvzL43ZVY-006irE; Fri, 07 Sep 2018 09:28:46 +0200 In-Reply-To: <87efe6iaws.fsf@mail.linkov.net> X-Provags-ID: V03:K1:Y4WR1uuxijM3XHGUEypjABU11ZspY7e/VysVM07afhAyNOFLujT Jt4xg9PXP26RreDkEfIVrgJS6Ntiuoril0VRYbTrN0bkKsEfmJ++sr3Gg5YSG+AtdDEUPFz GT+drOuDbSsmQ6IY9Mk3Hl4dkYf4xaaKl0zNA9p5p9InQKwCkjgqPutU1DbkEkrKV3SEBFR lJm1kql4mTDFFEmd3cvXQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:aecsjKHIchY=:eN5MYOFpNfBylvqCNH/ZvH ATEMfvjavUf4IZiWIvaEcac00IMDlUsr0B/lo25DF3zAapeTUg/TjQm6TrgCe/KDb3105p3Xp qKP2Aym1+1hZrvMbVLVi9xOR1LfrIdHGEute8e2tPSqNgtV3DFsTQwTMbnJNRZWkMVGYBCysc XZj4K0/4e+RAe4hWFhGIDXQy+swkqKc6WnCOesc4Vg1AliThHGTO5onfiN9lTQF5rscpLahlR sVf4wBfuFF6tWbP2XCw7ComqAxxv58lxEhJbtI8e4n36090HsK2sAItgfKzyDUoJf2dsL7C+D dp5tnt7gizvlthNAqEV2rRYtUO3czIQVGdEtnDYOIi7H8gK/g5Cv5ghMhWb31v04HiINTI22O dbj24Ie2TYkppj0jn5xEmUxi+mnjjm5FScqxNRS1yHYrD/sWUx2Xx0vjzPu0xrhYNB6gIMMBM 7sIO46CANsGVJzRO6I+MrFmpIvfB0pBITQYeJqw64qlTPG0LaPdtr2iQ/BCPW1YBkB0Ev5N/Q +Xln5hZLgYE9foL0wHFoQjKV+TP2IKrqRP6iax3ZEgmP1vjQid4TVWRaIXxqSE6R5Pw6bQO1L iHygjtLtBVyNK2QUfWYGn2Yg5H9OzsUOC0ZV1KdzikmPnFbHmC7i3Qycj5k+kIHrOWait6QC8 S0XTeQ1cqG5K6cvKjh2g2Zq2SF4OSM/SgKfVmaUlN2lfhaLbrRCVbP3wdA7Tj2SpDnZDnE1Ar 2j7a08PF1vH+BVNENoXFyi4esEpfP3iWQx2ZDQ1Co4yKItt0cgFgY4BbsfRms9j3aCXeg0jv 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: 208.118.235.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:150109 Archived-At: > The special case is in next-error-no-select. Its purpose is to display > the next-error buffer (the buffer with the location of the next-error), > not to display next-error-last-buffer (the buffer with the list of errors) > because next-error-last-buffer is already displayed. The user runs > next-error-no-select from the selected window that already displays > next-error-last-buffer, there is no need to try and display the same > buffer again. This behavior is not even documented. So pop-to-buffer > is useless here. But I suspect that maybe it was added for some use cases > to ensure that next-error-last-buffer is displayed. So at least > we need to make it harmless. But currently it makes harm with the > reported configuration. I provided a patch to fix next-error-no-select > to not fail with the legitimate user configuration. I suppose the idea is to implicitly emphasize the "-no-select" postfix by showing 'next-error-buffer' somewhere and simultaneously selecting a window showing 'next-error-last-buffer'. That's a rather unpleasant hack, your analysis is correct and 'display-buffer-overriding-action' is a valid remedy here (it's at least as good as (unless (get-buffer-window next-error-last-buffer) (pop-to-buffer next-error-last-buffer)) IMHO) so install it. martin