From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#28864: 25.3.50; next-error-no-select does select Date: Sun, 29 Oct 2017 01:42:23 +0300 Message-ID: <8c097da6-3396-0939-667c-cf50aafba689@yandex.ru> References: <87bml72qck.fsf@gmail.com> <4045abe7-1acb-314b-b9ac-72b62db30570@yandex.ru> <87sheh270d.fsf@gmail.com> <6f3b7c2c-31af-8eb2-8f13-a9ba17d3d8e6@yandex.ru> <87mv4m5lok.fsf@gmail.com> <87d15h5f97.fsf@gmail.com> <87wp3fxac4.fsf@localhost> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1509230594 7217 195.159.176.226 (28 Oct 2017 22:43:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 28 Oct 2017 22:43:14 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Thunderbird/56.0 Cc: 28864@debbugs.gnu.org, Noam Postavsky To: Juri Linkov , Tino Calancha Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Oct 29 00:43:09 2017 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 1e8Zop-000189-9P for geb-bug-gnu-emacs@m.gmane.org; Sun, 29 Oct 2017 00:43:07 +0200 Original-Received: from localhost ([::1]:34207 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e8Zow-0002F0-Jf for geb-bug-gnu-emacs@m.gmane.org; Sat, 28 Oct 2017 18:43:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34875) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e8Zon-0002Eq-5U for bug-gnu-emacs@gnu.org; Sat, 28 Oct 2017 18:43:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e8Zok-00015f-36 for bug-gnu-emacs@gnu.org; Sat, 28 Oct 2017 18:43:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:59111) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e8Zoj-00015R-Uz for bug-gnu-emacs@gnu.org; Sat, 28 Oct 2017 18:43:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e8Zoj-00014G-Is for bug-gnu-emacs@gnu.org; Sat, 28 Oct 2017 18:43:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 28 Oct 2017 22:43:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 28864 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 28864-submit@debbugs.gnu.org id=B28864.15092305544067 (code B ref 28864); Sat, 28 Oct 2017 22:43:01 +0000 Original-Received: (at 28864) by debbugs.gnu.org; 28 Oct 2017 22:42:34 +0000 Original-Received: from localhost ([127.0.0.1]:39559 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e8ZoI-00013X-4b for submit@debbugs.gnu.org; Sat, 28 Oct 2017 18:42:34 -0400 Original-Received: from mail-wm0-f51.google.com ([74.125.82.51]:44891) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e8ZoG-00013J-4i for 28864@debbugs.gnu.org; Sat, 28 Oct 2017 18:42:32 -0400 Original-Received: by mail-wm0-f51.google.com with SMTP id n74so5243507wmi.1 for <28864@debbugs.gnu.org>; Sat, 28 Oct 2017 15:42:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=kVWs5c8jBXj4esFV6cfMCh7RBzVS/IMv9HlI4hBl2yQ=; b=Wy+JG4Whj3AgiOz1BPjJr79/Ot5KN9CGsldPoUg0U86omTajJ4UstBffyGqeXVT7y0 fSZ5I5WPAqkX68N/69aSCHwr8I1GTRGUS4tiz/dkll3osYJ5uJWDi31r1Dzujv3lAEMi IG9Q56RgMFjRDxianXTLkn9wTysIg/+4NWq9e8ivGOi5V3rBPPE67vdqoj35RKVP9zTN C5WMUZg9xrO80YmczwWrh/aF6hCrIhyU7TM1MvZ9d1WakRRfAZWEa9fWJQHTWEPFEnZw wmrc8m0fDH/7UeErUWO58JX9e3oT21VxegGr0HAELBvRj82HIKrQ1//TkP8dUdKZKly1 OWYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=kVWs5c8jBXj4esFV6cfMCh7RBzVS/IMv9HlI4hBl2yQ=; b=bTvlo/rOm7CQfQ6eupbLu+dkxzvNA+welzcz4RXg+pyOO3VqsjWNyVtV9oP2RBZNW3 he5dkiW5NbTfBB5/nI5Pf7F+bUpSrV8/aYEpF+n0JHl+BCElSb+Q0Ujw6uulglvDNtjn THUY989dUvNaiCKT3j1eGUdsiMNwLY/cx6Oa/QG+vsp6qGP1oAFrc42BVlJKo2FyRikK pUfy6O/Y1sHLHJB0aWgYvuJ561vJ31svdkGpVpshmt+t+Uxevr7Qf4u0ynLx/SvDE7iG 707afeeiaa3OO3IjntAieA3xLcet3MzNGnMVNhGI5e3V2I8Zv6nmNIfvGVGRvNrtDjpa ursQ== X-Gm-Message-State: AMCzsaWcOPbsmK6XFlqtNFQ4i4M4Y0QD3FtznfKkx48fO7sYhgstxVDA B/MwFu7xnhPhrjZ60oN5fgo= X-Google-Smtp-Source: ABhQp+SkPobP47VA468N7kvE3ZEznsOVchd7GzFhc+iDiy/H4tQJoVFawedDCiITTqDedxLpS1hexw== X-Received: by 10.28.84.89 with SMTP id p25mr234751wmi.112.1509230546286; Sat, 28 Oct 2017 15:42:26 -0700 (PDT) Original-Received: from [192.168.1.3] ([185.105.174.193]) by smtp.googlemail.com with ESMTPSA id c3sm6998520wrd.44.2017.10.28.15.42.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 Oct 2017 15:42:25 -0700 (PDT) In-Reply-To: <87wp3fxac4.fsf@localhost> Content-Language: en-US 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:139134 Archived-At: On 10/28/17 11:54 PM, Juri Linkov wrote: > Please don't remove next-error-last-buffer from change-log-mode. > Actually it is legitimate use according to the documentation > of next-error-last-buffer: > "The most recent ‘next-error’ buffer. > A buffer becomes most recent when its compilation, grep, or > similar mode is started, or when it is used with \\[next-error]." The fact that it's documented doesn't exactly mean that the behavior really makes sense or is optimal. > The problem occurred because two next-error buffer windows (*grep* and > next-error capable ChangeLog) were both visible on the selected frame, > but I believe we could fix this in the inner logic of next-error. We've discussed the visibility-based selection before, I still don't think it makes sense, and the present bug report is evidence.