From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: conflicting uses of next-error-function Date: Wed, 29 Apr 2015 20:40:39 +0300 Message-ID: <55411797.2090704@yandex.ru> References: <83zja6b3tc.fsf@gnu.org> <54A24079.4020902@yandex.ru> <54A2FF47.6010207@yandex.ru> <54A86135.7080004@yandex.ru> <54A90002.7080009@gmx.at> <54A9C3FB.7000602@yandex.ru> <54AA3881.3080304@gmx.at> <54ABBB47.7010603@yandex.ru> <837fszx7iy.fsf@gnu.org> <83r3r5wqwv.fsf@gnu.org> <83k2wxwexb.fsf@gnu.org> <83fv7kwbow.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1430329274 18713 80.91.229.3 (29 Apr 2015 17:41:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 29 Apr 2015 17:41:14 +0000 (UTC) Cc: emacs-devel@gnu.org To: Helmut Eller , Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 29 19:40:59 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 1YnVyk-0007bF-S6 for ged-emacs-devel@m.gmane.org; Wed, 29 Apr 2015 19:40:58 +0200 Original-Received: from localhost ([::1]:40324 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnVyk-0001TB-2s for ged-emacs-devel@m.gmane.org; Wed, 29 Apr 2015 13:40:58 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46515) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnVyg-0001Sj-Sx for emacs-devel@gnu.org; Wed, 29 Apr 2015 13:40:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnVyd-0007FU-4L for emacs-devel@gnu.org; Wed, 29 Apr 2015 13:40:54 -0400 Original-Received: from mail-wg0-x22d.google.com ([2a00:1450:400c:c00::22d]:34030) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnVyc-0007D4-TU for emacs-devel@gnu.org; Wed, 29 Apr 2015 13:40:51 -0400 Original-Received: by wgso17 with SMTP id o17so36471066wgs.1 for ; Wed, 29 Apr 2015 10:40:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=aXrhdgITFJ9cFPeqMgmxLj94rEl9lcYhUEUniyF2ImA=; b=YXdPo7ngY35rGCn/emyG/QzcC4WWseccmXfIHWgwpNbGbrZsnoXVpkziW0wnbn1sNA X7WCgT4JfU3Zbrdwh4QojMKdWY0j8LkGr/v2wFY4B29oQTVwl4etc7Wsfkot0j2++FL9 pxUUVY9iHSjWZAcFITh3RslPhhejZ7QqjLNpernj6raZEjQei0Cn/a/n+DWlLmL5wh4S /tPvbTpRlyfvn2Zqde0DSD9wMMJ7nP1k4sqIhtlv5Fx+E75rrn3woOMnLIroznPZC7gx 2N0yl3p4FxImSEbM2W6FZUaHLPyc5MAlN3N51u5DyHd2D9ZFyEmMiPZmg/xGDYqYuXSX 79UA== X-Received: by 10.194.234.38 with SMTP id ub6mr398031wjc.9.1430329240753; Wed, 29 Apr 2015 10:40:40 -0700 (PDT) Original-Received: from [192.168.0.185] (static-nbl2-118.cytanet.com.cy. [212.31.107.118]) by mx.google.com with ESMTPSA id l20sm39963704wjw.42.2015.04.29.10.40.40 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Apr 2015 10:40:40 -0700 (PDT) user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 in-reply-to: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::22d 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:186037 Archived-At: On 04/29/2015 07:58 PM, Helmut Eller wrote: > Maybe we could mark a buffer somehow that it's a reasonable candidate for > next-error-last-buffer and have a command ala switch-buffer to select > the current next-error-buffer from the list of candidates. Yes, that sounds like the easiest approach. Then using next-error-function in xref at least won't make things worse. The "mark a buffer somehow that it's a reasonable candidate" is an important step, because even plain buffers can have local next-error-function values, set by Flycheck or Flymake, for instance. How will we do that?