GNU bug report logs - #42981
void function next-error-found

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 42981 in the body.
You can then email your comments to 42981 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Philip K." <philipk <at> posteo.net>
To: bug-gnu-emacs <at> gnu.org
Subject: void function next-error-found
Date: Sat, 22 Aug 2020 08:12:26 +0200

Hi,

I'm using Emacs 26.3 again, and while testing project-search, I noticed
that an error is signalled by Xref (1.0.2) use of the function
next-error-found, that hasn't been defined as of 26.3. As Xref promises
compatibility with 26.3, it seems that next-error-found should be
replaced with something more backwards compatible.

-- 
	Philip K.

Message #8 received at 42981 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: "Philip K." <philipk <at> posteo.net>, 42981 <at> debbugs.gnu.org,
 Juri Linkov <juri <at> linkov.net>
Subject: Re: bug#42981: void function next-error-found
Date: Wed, 26 Aug 2020 00:46:46 +0300

Hi Philip,

On 22.08.2020 09:12, Philip K. wrote:

> I'm using Emacs 26.3 again, and while testing project-search, I noticed
> that an error is signalled by Xref (1.0.2) use of the function
> next-error-found, that hasn't been defined as of 26.3. As Xref promises
> compatibility with 26.3, it seems that next-error-found should be
> replaced with something more backwards compatible.

Thanks for another important find.

Juri, do you remember what we should call/do instead in Emacs 26?

Message #11 received at 42981 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: "Philip K." <philipk <at> posteo.net>, 42981 <at> debbugs.gnu.org
Subject: Re: bug#42981: void function next-error-found
Date: Wed, 26 Aug 2020 21:40:27 +0300

>> I'm using Emacs 26.3 again, and while testing project-search, I noticed
>> that an error is signalled by Xref (1.0.2) use of the function
>> next-error-found, that hasn't been defined as of 26.3. As Xref promises
>> compatibility with 26.3, it seems that next-error-found should be
>> replaced with something more backwards compatible.
>
> Thanks for another important find.
>
> Juri, do you remember what we should call/do instead in Emacs 26?

Hmm, AFAIR there was nothing before adding next-error-found
for Emacs 27 in 0c9e3df3c2.  So you could just make its call
conditional, or copy the current body of next-error-found,
removing some new variables like next-error-found-function,
or just use (setq next-error-last-buffer (or from-buffer (current-buffer)))

Message #16 received at 42981-done <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Juri Linkov <juri <at> linkov.net>
Cc: "Philip K." <philipk <at> posteo.net>, 42981-done <at> debbugs.gnu.org
Subject: Re: bug#42981: void function next-error-found
Date: Thu, 27 Aug 2020 00:57:36 +0300

On 26.08.2020 21:40, Juri Linkov wrote:
> or just use (setq next-error-last-buffer (or from-buffer (current-buffer)))

Done that now, thanks.

This should work now (xref 1.0.3 should be built soon), but Philip, 
please let us know if something is still amiss.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.