From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: conflicting uses of next-error-function Date: Mon, 04 May 2015 18:21:00 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <877fso6l2r.fsf@lifelogs.com> References: <83zja6b3tc.fsf@gnu.org> <83r3r5wqwv.fsf@gnu.org> <83k2wxwexb.fsf@gnu.org> <83fv7kwbow.fsf@gnu.org> <55411797.2090704@yandex.ru> <554165C5.2090301@yandex.ru> <5541E20F.9000602@yandex.ru> <55455BD0.50508@yandex.ru> <55460A64.4060407@yandex.ru> <55462CDA.5040300@yandex.ru> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1430778070 992 80.91.229.3 (4 May 2015 22:21:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 May 2015 22:21:10 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 05 00:21:01 2015 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 1YpOjV-0000W5-5X for ged-emacs-devel@m.gmane.org; Tue, 05 May 2015 00:21:01 +0200 Original-Received: from localhost ([::1]:36160 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpOjU-0004L4-3l for ged-emacs-devel@m.gmane.org; Mon, 04 May 2015 18:21:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36004) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpOjQ-0004Ky-Qv for emacs-devel@gnu.org; Mon, 04 May 2015 18:20:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YpOjL-0002VC-TN for emacs-devel@gnu.org; Mon, 04 May 2015 18:20:56 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:42578) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YpOjL-0002V8-Mj for emacs-devel@gnu.org; Mon, 04 May 2015 18:20:51 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YpOjK-0000PQ-CN for emacs-devel@gnu.org; Tue, 05 May 2015 00:20:50 +0200 Original-Received: from c-98-229-61-72.hsd1.ma.comcast.net ([98.229.61.72]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 May 2015 00:20:50 +0200 Original-Received: from tzz by c-98-229-61-72.hsd1.ma.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 05 May 2015 00:20:50 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 19 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-98-229-61-72.hsd1.ma.comcast.net X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:qt8xomcugdgkcW6Xc5uf5JA8C4k= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:186211 Archived-At: On Sun, 3 May 2015 17:12:42 +0300 Dmitry Gutov wrote: DG> Here's the problem: with global-flycheck-mode on, all emacs-lisp-mode DG> buffers have next-error-function set locally (to DG> flycheck-next-error-function). And that function navigates between DG> byte-compilation errors and warnings within the current buffer, which DG> is very much in line with the next-error-function docstring (which DG> says "find the next error in the current buffer"). DG> Thus quite often next-error-find-buffer will return any DG> emacs-lisp-mode buffer (for instance, when it's the only one visible DG> in the current frame). If we remember all such buffers, If we agree to implement a `next-error-priority', then perhaps `next-error-find-buffer' should penalize buried buffers by subtracting from their priority. Thus buffers most recently buried will have the lowest priority. Ted