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: Wed, 29 Apr 2015 20:15:50 +0200 Message-ID: References: <83zja6b3tc.fsf@gnu.org> <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> <55411797.2090704@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1430331365 23572 80.91.229.3 (29 Apr 2015 18:16:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 29 Apr 2015 18:16:05 +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 Wed Apr 29 20:16:04 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 1YnWWe-0002qU-Rq for ged-emacs-devel@m.gmane.org; Wed, 29 Apr 2015 20:16:00 +0200 Original-Received: from localhost ([::1]:40432 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnWWe-0002aC-2V for ged-emacs-devel@m.gmane.org; Wed, 29 Apr 2015 14:16:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54775) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnWWa-0002a5-Mn for emacs-devel@gnu.org; Wed, 29 Apr 2015 14:15:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnWWX-00029W-Cp for emacs-devel@gnu.org; Wed, 29 Apr 2015 14:15:56 -0400 Original-Received: from mail-wi0-x231.google.com ([2a00:1450:400c:c05::231]:38308) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnWWX-00029S-5w for emacs-devel@gnu.org; Wed, 29 Apr 2015 14:15:53 -0400 Original-Received: by wiun10 with SMTP id n10so75617632wiu.1 for ; Wed, 29 Apr 2015 11:15:52 -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=1lZtahUa1201+C921RCli2lzK9bs2Ss0jkslEl4hexw=; b=CpQOJpBQgFPpOFmrR6GtYhEOB4aXntQk+Fai78TVuTa/Ti9czspH8JxjT5hira8Ije nMbzc6uFpCvLV6IX2zAyGZAnKxeDzs3POgNZZ67us/qR9npoLa+ntkVw+rBRi3qtUUMn Nfd9PtkpCTA6XASPMyImgOKajh1G7Zp2qpWYGOwZ54mLL5KZ9AkLILAQesJn/rSdNPUU obanwmYag6uWCpu1I/RdNV4JLOq3s/MXwNv1sXzfbztzHhHKsuYyzj0nw5dU8wYcafYB cSNbWcKNo8TjKjSP++ax+wya/EeDyZhy6+Z6lBUPkVXimj1RUpRU8+iw4TZXW+knwvrz b/dA== X-Received: by 10.180.86.69 with SMTP id n5mr8057277wiz.91.1430331352642; Wed, 29 Apr 2015 11:15:52 -0700 (PDT) Original-Received: from ix (dial-185099.pool.broadband44.net. [212.46.185.99]) by mx.google.com with ESMTPSA id ub1sm40083769wjc.43.2015.04.29.11.15.51 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Apr 2015 11:15:51 -0700 (PDT) Original-Received: from helmut by ix with local (Exim 4.84) (envelope-from ) id 1YnWWU-000791-PF; Wed, 29 Apr 2015 20:15:50 +0200 In-Reply-To: <55411797.2090704@yandex.ru> (Dmitry Gutov's message of "Wed, 29 Apr 2015 20:40:39 +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:c05::231 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:186041 Archived-At: On Wed, Apr 29 2015, Dmitry Gutov wrote: > 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? I would just use a buffer local variable, like next-error-buffer-p, or perhaps somebody can come up with a more catchy name. It might be nifty (but more complicated) to organize those buffers as a stack or ring so that a context can be pushed/popped; if so then it might be useful to use an integer instead of a boolean as value for this buffer local variable. Helmut