Problem in 9.3: (next-error) broken

Problem in 9.3: (next-error) broken

[Tory S. Anderson]

Running 9.3 as included in emacs 27, I have found a breaking error that I am not sure how to debug any further. Here's my workflow:

1 or 2. Execute (find-grep) for something that brings results
1 or 2. Switch to an orgmode buffer
3. Attempt C-` (next-error)

Result: user-error: No more matches

Switch to a non-org buffer and try again -- it works properly, even without re-grepping.

This error DID occur in emacs -Q, so it shouldn't be the result of any competing packages.

Any suggestions to recover my workflow?

Thanks,

- Tory

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

[Tory S. Anderson]

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.

"Tory S. Anderson" <tory_anderson@byu.edu> writes:

> Running 9.3 as included in emacs 27, I have found a breaking error that I am not sure how to debug any further. Here's my workflow:
>
> 1 or 2. Execute (find-grep) for something that brings results
> 1 or 2. Switch to an orgmode buffer
> 3. Attempt C-` (next-error)
>
> Result: user-error: No more matches
>
> Switch to a non-org buffer and try again -- it works properly, even without re-grepping.
>
> This error DID occur in emacs -Q, so it shouldn't be the result of any competing packages.
>
> Any suggestions to recover my workflow?
>
> Thanks,
>
> - Tory

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

[Kyle Meyer]

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.

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

[Tory S. Anderson]

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.

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

[Kyle Meyer]

Tory S. Anderson writes:

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

next-error-function is set in the define-derived-mode body for org-mode,
so something like

    (add-hook 'org-mode-hook
              (lambda () (setq next-error-function nil)))

should work, and it appears to on my end.