emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alain.Cochard@unistra.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: 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	[thread overview]
Message-ID: <877eo3tl5o.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <23292.16161.349325.297641@frac.u-strasbg.fr> (Alain Cochard's message of "Wed, 16 May 2018 16:24:33 +0200")

Hello,

Alain.Cochard@unistra.fr 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

next prev parent reply	other threads:[~2018-05-16 20:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16 14:24 Should org-complete-tags-always-offer-all-agenda-tags be documented in the manual? [was: Tag completion does not work well with ...] Alain.Cochard
2018-05-16 20:12 ` Nicolas Goaziou [this message]
2018-05-17 11:17   ` Alain.Cochard
2018-05-19 11:53     ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877eo3tl5o.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=Alain.Cochard@unistra.fr \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).