Fix: (org-ql-find) Go to base buffer if possible
Use the base buffer if it has one, because if we run the search from an indirect buffer, it's likely already narrowed to a different entry, and making an indirect buffer from that one would end up with a restriction that would likely hide the selected entry.
This commit is contained in:
parent
0168171a14
commit
34f8b75b35
3 changed files with 50 additions and 41 deletions
|
|
@ -75,7 +75,8 @@ single predicate)."
|
|||
:query-prefix query-prefix
|
||||
:query-filter query-filter
|
||||
:prompt prompt)))
|
||||
(set-buffer (marker-buffer marker))
|
||||
(set-buffer (or (buffer-base-buffer (marker-buffer marker))
|
||||
(marker-buffer marker)))
|
||||
(pop-to-buffer (current-buffer) org-ql-find-display-buffer-action)
|
||||
(without-restriction
|
||||
(goto-char marker)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue