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
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
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
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" writes:
> Running 9.3 as included in emacs 27, I have found a breaking
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
