On 2023-08-11 23:48, Ihor Radchenko wrote:
- If you run into this issue, the real pain is to understand what's
going on, since org-ctags might get loaded in surprising ways. So
probably we should make that easier.
The quick fix is unsetting `help-enable-completion-autoload'.
Jens Schmidt writes:
> - If you run into this issue, the real pain is to understand what's
>going on, since org-ctags might get loaded in surprising ways. So
>probably we should make that easier.
The quick fix is unsetting `help-enable-completion-autoload'.
And I do not think that we
On 2023-08-11 19:01, Nick Dokos wrote:
Sure, but we should not reject Jens' proposal just because of this
argument. We can use the suggestions to improve org-ctags itself, after
it is explicitly loaded.
Absolutely.
My disagreement was only with the part that I quoted, in particular
the
Ihor Radchenko writes:
> Nick Dokos writes:
>
>>> ...
>>> Probably the problem is not the side-effects done by loading
>>> =org-ctags=, but rather that these hook function from =org-ctags= try
>>> to do their job when the environment is not really ready for them,
>>> i.e. when there is no known
Nick Dokos writes:
>> ...
>> Probably the problem is not the side-effects done by loading
>> =org-ctags=, but rather that these hook function from =org-ctags= try
>> to do their job when the environment is not really ready for them,
>> i.e. when there is no known tag file around.
>> ...
>
> I
Jens Schmidt writes:
> On 2023-08-08 10:48, Ihor Radchenko wrote:
>
> ...
> Probably the problem is not the side-effects done by loading
> =org-ctags=, but rather that these hook function from =org-ctags= try
> to do their job when the environment is not really ready for them,
> i.e. when there
On 2023-08-08 10:48, Ihor Radchenko wrote:
The situation is a bit more complex.
To make it even more complex, here a different point of view. Sorry,
I don't have any earlier mails ready I could reply to ...
* TL;DR
Probably the problem is not the side-effects done by loading
=org-ctags=,
