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: Thu, 30 Apr 2015 08:19:24 +0200 Message-ID: References: <83zja6b3tc.fsf@gnu.org> <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> <554165C5.2090301@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1430374777 20808 80.91.229.3 (30 Apr 2015 06:19:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 30 Apr 2015 06:19:37 +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 Thu Apr 30 08:19:37 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 1Ynhou-0005N6-GG for ged-emacs-devel@m.gmane.org; Thu, 30 Apr 2015 08:19:36 +0200 Original-Received: from localhost ([::1]:42206 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ynhot-0001Ga-GY for ged-emacs-devel@m.gmane.org; Thu, 30 Apr 2015 02:19:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57013) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ynhoq-0001GV-8U for emacs-devel@gnu.org; Thu, 30 Apr 2015 02:19:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ynhom-0000Eq-5P for emacs-devel@gnu.org; Thu, 30 Apr 2015 02:19:32 -0400 Original-Received: from mail-wg0-x232.google.com ([2a00:1450:400c:c00::232]:34667) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ynhol-0000El-Up for emacs-devel@gnu.org; Thu, 30 Apr 2015 02:19:28 -0400 Original-Received: by wgso17 with SMTP id o17so50773836wgs.1 for ; Wed, 29 Apr 2015 23:19:27 -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=TAMTXvJx4FoPZOQz3vwZM79euYGHbsN+HqSToubBZUU=; b=EpxIfxKWIZsEk/uPDLu+I5owIvpapwF400R8OesYpxt7YaiAUQq20inamsx+Khe/NM 7Snjgbsth7yt8swDfs9MV+ho1JWH2EsHN/7kUbZ1EkzY5FvSaQ5M1Zq5GzHlf1nETRLg 1xAXUNcBOv2gGk5o5wtRhkWQVsSQ9xMsxW88Rwq4fHSasfu1n83RYXqxFR3sWg9BBZwp xGY5YWncCgz2UfeGXEwFTsFdGOxnViAM2ScPLuZIfMOmjscH76m+tKOQnIOvDZX58Lv+ kgraZ3sS+RdzswnhQ79emvz2JUrbiT7PSRSOLl0sULUImU01wS7dE67F7fivB2xT4baU oVmQ== X-Received: by 10.194.133.71 with SMTP id pa7mr5212991wjb.155.1430374767403; Wed, 29 Apr 2015 23:19:27 -0700 (PDT) Original-Received: from ix (dial-185099.pool.broadband44.net. [212.46.185.99]) by mx.google.com with ESMTPSA id ao4sm1735717wjc.14.2015.04.29.23.19.26 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Apr 2015 23:19:26 -0700 (PDT) Original-Received: from helmut by ix with local (Exim 4.84) (envelope-from ) id 1Ynhoi-0000W2-A0; Thu, 30 Apr 2015 08:19:24 +0200 In-Reply-To: <554165C5.2090301@yandex.ru> (Dmitry Gutov's message of "Thu, 30 Apr 2015 02:14:13 +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:186052 Archived-At: On Thu, Apr 30 2015, Dmitry Gutov wrote: > Yup, a ring might be a replacement for both next-error-last-buffer and > next-error-buffer-p. But when will buffers be popped from it? Maybe never, or more precisely: dead buffers in the ring are ignored and removed automatically. I don't know what the issue with flymake is but it would certainly be nice if this would work without having to update existing clients. Helmut