From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Helmut Eller Newsgroups: gmane.emacs.devel Subject: Re: conflicting uses of next-error-function Date: Sun, 03 May 2015 08:54:11 +0200 Message-ID: References: <83zja6b3tc.fsf@gnu.org> <54AA3881.3080304@gmx.at> <54ABBB47.7010603@yandex.ru> <837fszx7iy.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> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1430636065 26760 80.91.229.3 (3 May 2015 06:54:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 3 May 2015 06:54:25 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 03 08:54:24 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 1YonnD-0005FL-Vp for ged-emacs-devel@m.gmane.org; Sun, 03 May 2015 08:54:24 +0200 Original-Received: from localhost ([::1]:58516 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YonnD-0003F5-0n for ged-emacs-devel@m.gmane.org; Sun, 03 May 2015 02:54:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41554) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yonn9-0003Ep-24 for emacs-devel@gnu.org; Sun, 03 May 2015 02:54:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yonn5-0004Z9-S2 for emacs-devel@gnu.org; Sun, 03 May 2015 02:54:18 -0400 Original-Received: from mail-wg0-x232.google.com ([2a00:1450:400c:c00::232]:34610) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yonn5-0004Y5-L5 for emacs-devel@gnu.org; Sun, 03 May 2015 02:54:15 -0400 Original-Received: by wgso17 with SMTP id o17so123241076wgs.1 for ; Sat, 02 May 2015 23:54:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=7tCNuEqvNX5FIS9gSiVGeo27tbYqP16AFl4xXKAkCBw=; b=lwK9YrKGJ74ehp4Q2DJGfZBKW+z04197iExn15oT7BIq1zkNk+hOv2G72aKrjwsct9 rzGXoJ8wVkm6GH86QIvRHRFfGC91Je1faLfSM3avM+jQnwkADVJ3LYEHBFkMf5iza0E/ MSVa1iaseOBG7Pqz/dQySN6zoaaB+KAVUROfP0EcczbMhBb1KxkFV+mFO3YcMNmT7yd/ IoysV2/jC5RSjT6w8L/CSaHBt3w7cp7algCaQ1KoxULXKaDrdUotuYDW9n+uazxcie5X loLJ2UwOh9vjyITX61JGjAuLR9drBhzzcsP2ZYi5TGy1GmKGdudF5zqzcejOYW6UXgkJ gePQ== X-Received: by 10.180.187.12 with SMTP id fo12mr9950544wic.40.1430636054892; Sat, 02 May 2015 23:54:14 -0700 (PDT) Original-Received: from ix ([212.46.170.210]) by mx.google.com with ESMTPSA id ez19sm5366665wid.19.2015.05.02.23.54.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 May 2015 23:54:13 -0700 (PDT) Original-Received: from helmut by ix with local (Exim 4.84) (envelope-from ) id 1Yonn1-0000Wv-Sg; Sun, 03 May 2015 08:54:12 +0200 In-Reply-To: <55455BD0.50508@yandex.ru> (Dmitry Gutov's message of "Sun, 3 May 2015 02:20:48 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::232 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:186154 Archived-At: On Sun, May 03 2015, Dmitry Gutov wrote: > On 04/30/2015 08:46 PM, Helmut Eller wrote: > >> next-error calls next-error-find-buffer. Maybe we could record every >> buffer that was returned by next-error-find-buffer and include them in >> the candidate list. > > That's not terrible, but then we have almost the same two non-ideal choices: > > - Only record the buffers that have even been noticed as the value of > next-error-last-buffer. This way we'll ignore e.g. Compilation buffers > that have never had a chance to be used with `next-error'. > > - Record all buffers that ever were returned from that function. This > will also include normal (file-visiting) buffers where > next-error-function is set locally (and usually only points to > locations within that buffer). I was thinking of adding a new function like (next-error-note-buffer BUFFER &optional DONT-SELECT) that essentially replaces next-error-last-buffer for those packages that bother to use it AND to add some degree of backward compatibility by recording the buffer returned by next-error-find-buffer. Helmut