[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Should org-complete-tags-always-offer-all-agenda-tags be documen
From: |
Nicolas Goaziou |
Subject: |
Re: [O] Should org-complete-tags-always-offer-all-agenda-tags be documented in the manual? [was: Tag completion does not work well with ...] |
Date: |
Wed, 16 May 2018 22:12:19 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) |
Hello,
address@hidden writes:
> In general, though, I still feel it would make sense to document it,
> especially considering that other ways than the default are already
> documented. Consider this excerpt from section "6.2 Setting tags":
>
> Org supports tag insertion based on a _list of tags_. By
> default this list is constructed dynamically, containing all tags
> currently used in the buffer. You may also globally specify a hard
> list of tags with the variable ‘org-tag-alist’. Finally you can
> set the default tags for a given file [...]
>
> One could have a footnote after "currently used in the buffer" which
> could be something like:
>
> One can have this list contain all tags used in all agenda files
> (see [[link to section "6.4 Tag searches"]]) by customizing
> variable org-complete-tags-always-offer-all-agenda-tags.
I have no objection to this, but why is the link to section "Tag
searches" on topic here?
Regards,
--
Nicolas Goaziou