Joseph Turner writes:
>> We generally agree that (require 'org-ctags) should ideally not have
>> side effects, but do not want to introduce too breaking changes either.
>
> Does this mean that org-ctag's disruptive behavior will be fixed?
Yeah. But it is quite far down in my todo-list now
Rudolf Adamkovič writes:
> Joseph Turner writes:
>
>> (setopt org-ctags-open-link-functions nil)
>
> Oh, thank you! This regularly drives me crazy.
You're welcome!
> I added the following to my Emacs/Org configuration:
>
> #+BEGIN_SRC emacs-lisp :results none
> (eval-after-load 'org-ctags
Joseph Turner writes:
> (setopt org-ctags-open-link-functions nil)
Oh, thank you! This regularly drives me crazy.
I added the following to my Emacs/Org configuration:
#+BEGIN_SRC emacs-lisp :results none
(eval-after-load 'org-ctags
(setq org-ctags-open-link-functions nil))
#+END_SRC
Rudy
Ihor Radchenko writes:
> Joseph Turner writes:
>
>> When org-ctags-find-tag is a member of org-open-link-functions, fuzzy
>> links and custom-id links are broken. Instead of following those links,
>> Emacs prompts for a filename with "Visit tags table (default TAGS)".
>
> This is expected. As
Joseph Turner writes:
> When org-ctags-find-tag is a member of org-open-link-functions, fuzzy
> links and custom-id links are broken. Instead of following those links,
> Emacs prompts for a filename with "Visit tags table (default TAGS)".
This is expected. As per org-ctags documentation:
;; By
Hello!
When org-ctags-find-tag is a member of org-open-link-functions, fuzzy
links and custom-id links are broken. Instead of following those links,
Emacs prompts for a filename with "Visit tags table (default TAGS)".
To reproduce this issue with emacs -Q:
(require 'org-ctags)
Then open an
