unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#42981: void function next-error-found
@ 2020-08-22  6:12 Philip K.
  2020-08-25 21:46 ` Dmitry Gutov
  0 siblings, 1 reply; 4+ messages in thread
From: Philip K. @ 2020-08-22  6:12 UTC (permalink / raw)
  To: 42981


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.





^ permalink raw reply	[flat|nested] 4+ messages in thread

* bug#42981: void function next-error-found
  2020-08-22  6:12 bug#42981: void function next-error-found Philip K.
@ 2020-08-25 21:46 ` Dmitry Gutov
  2020-08-26 18:40   ` Juri Linkov
  0 siblings, 1 reply; 4+ messages in thread
From: Dmitry Gutov @ 2020-08-25 21:46 UTC (permalink / raw)
  To: Philip K., 42981, Juri Linkov

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?





^ permalink raw reply	[flat|nested] 4+ messages in thread

* bug#42981: void function next-error-found
  2020-08-25 21:46 ` Dmitry Gutov
@ 2020-08-26 18:40   ` Juri Linkov
  2020-08-26 21:57     ` Dmitry Gutov
  0 siblings, 1 reply; 4+ messages in thread
From: Juri Linkov @ 2020-08-26 18:40 UTC (permalink / raw)
  To: Dmitry Gutov; +Cc: Philip K., 42981

>> 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)))





^ permalink raw reply	[flat|nested] 4+ messages in thread

* bug#42981: void function next-error-found
  2020-08-26 18:40   ` Juri Linkov
@ 2020-08-26 21:57     ` Dmitry Gutov
  0 siblings, 0 replies; 4+ messages in thread
From: Dmitry Gutov @ 2020-08-26 21:57 UTC (permalink / raw)
  To: Juri Linkov; +Cc: Philip K., 42981-done

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.





^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-08-26 21:57 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-22  6:12 bug#42981: void function next-error-found Philip K.
2020-08-25 21:46 ` Dmitry Gutov
2020-08-26 18:40   ` Juri Linkov
2020-08-26 21:57     ` Dmitry Gutov

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).