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 15:25:45 +0200 Message-ID: References: <83zja6b3tc.fsf@gnu.org> <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> <55460A64.4060407@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1430659568 30907 80.91.229.3 (3 May 2015 13:26:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 3 May 2015 13:26:08 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 03 15:26:03 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 1YotuE-0002jN-HP for ged-emacs-devel@m.gmane.org; Sun, 03 May 2015 15:26:02 +0200 Original-Received: from localhost ([::1]:59307 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yotu8-0004rI-Vy for ged-emacs-devel@m.gmane.org; Sun, 03 May 2015 09:25:56 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50159) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yotu4-0004r9-Pg for emacs-devel@gnu.org; Sun, 03 May 2015 09:25:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yotu1-0003GT-LC for emacs-devel@gnu.org; Sun, 03 May 2015 09:25:52 -0400 Original-Received: from mail-wi0-x229.google.com ([2a00:1450:400c:c05::229]:33261) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yotu1-0003GB-EJ for emacs-devel@gnu.org; Sun, 03 May 2015 09:25:49 -0400 Original-Received: by wief7 with SMTP id f7so60065109wie.0 for ; Sun, 03 May 2015 06:25:48 -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=CKkbrG9G4SzAhQ95HktfgEZeO/mS8Tx3iPt5B+yuyKE=; b=gttdLu+0XM6JVu1edVeZH/A9UO+SPPJ/45yMdmojD8NCO7+B4T5hDXlcSL6qLGMYAh W23UwnxAYzawsq1TEpOn18HH1kVMuMA2jQOTolUtM4xLp3HUbv5t3mC81vInlkXKrukJ qfby2x8a6BMHgkNwqeQmcvXtNIMlGPJV/OZnGRn8cCLZxbCvqCaqT8Uyn9y2OnWT74yg 8NUd7QuiymbUFoh9G5VYGpN0bqA1Z5wMJ076Saoby2Fyp91ULSMGDpCzACAWoa9UZVzo B8EdqYmBTcVSyM44Ca4YpDQJ+QBWT8d947MvvmirbC/kXSagSz6Mj2bw/vxhIoOOQ2Rs RZ2g== X-Received: by 10.180.230.226 with SMTP id tb2mr11685159wic.64.1430659548272; Sun, 03 May 2015 06:25:48 -0700 (PDT) Original-Received: from ix ([212.46.170.210]) by mx.google.com with ESMTPSA id l6sm16102297wjz.4.2015.05.03.06.25.46 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 May 2015 06:25:47 -0700 (PDT) X-Google-Original-From: Helmut Eller Original-Received: from helmut by ix with local (Exim 4.84) (envelope-from ) id 1Yottx-0000XS-9Q; Sun, 03 May 2015 15:25:45 +0200 In-Reply-To: <55460A64.4060407@yandex.ru> (Dmitry Gutov's message of "Sun, 3 May 2015 14:45:40 +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::229 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:186159 Archived-At: On Sun, May 03 2015, Dmitry Gutov wrote: > On 05/03/2015 09:54 AM, Helmut Eller wrote: > >> 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. > > I'm not sure I understand your proposal. You seem to have ignored the > description of the "non-ideal choice" number two. Sorry, hadn't fully understood option two. Yes, it option two probably covers most cases that are relevant in practice. Helmut