Re: Problem in 9.3: (next-error) broken

["Tory S. Anderson" <tory_anderson@byu.edu>]

Perhaps I was on an old version, although I don't think it was that old.

In any case, I keep having org-occur-next-match set away from nil, and I'm actually having trouble figuring out which hook will fix it, since org-mode-hook doesn't seem to be doing it. Instead I end up manually evaluating =(setq next-error-function nil)= every time I need next-error.

Any suggestions?

Kyle Meyer <kyle@kyleam.com> writes:

> Tory S. Anderson writes:
>
>> I discovered teh cause of this error is that new versions of orgmode
>> sets next-error-function and so breaks the. I've added a hook to clear
>> this in orgmode and I can navigate my grep properly again.
>
> I'm not having any luck triggering the issue, but in any case there
> seems to be something missing from that explanation.  Org has set
> next-error-function to org-occur-next-match since dd2346134 (Implement
> next-error and previous-error functionality for sparse trees,
> 2011-01-06), and the definition of org-occur-next-match hasn't changed
> substantially since.