From: Alain.Cochard@unistra.fr
To: Nicolas Goaziou <mail@nicolasgoaziou.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: Thu, 17 May 2018 13:17:19 +0200 [thread overview]
Message-ID: <23293.25791.381801.813233@frac.u-strasbg.fr> (raw)
In-Reply-To: <877eo3tl5o.fsf@nicolasgoaziou.fr>
Nicolas Goaziou writes on Wed 16 May 2018 22:12:
> > 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.
> [...] why is the link to section "Tag searches" on topic here?
My reasoning was that, at section "6.2" and upon sequential reading,
the user does not really know what agenda files are yet. I was hoping
that the excerpt:
‘C-c a m (org-tags-view)’
Create a global list of tag matches from all agenda files.
*Note Matching tags and properties::.
could him to get acquainted with the concept. In fact I hesitated
between this link and, as is sometimes done in similar cases, the link
to "10 Agenda views"[fn:1], but which I found too general.
But perhaps it is not pertinent to assume sequential reading. Or
perhaps (a digest of) "10 Agenda views" should appear earlier in the
manual.
Regards,
alain
[fn:1] e.g., in "5.1 Basic TODO functionality":
‘C-c a t (org-todo-list)’
Show the global TODO list. Collects the TODO items (with not-DONE
states) from all agenda files (*note Agenda views::) into a single
buffer.
--
EOST (École et Observatoire des Sciences de la Terre)
IPG (Institut de Physique du Globe) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | Fax: +33 (0)3 68 85 01 25
next prev parent reply other threads:[~2018-05-17 11:17 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
2018-05-17 11:17 ` Alain.Cochard [this message]
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=23293.25791.381801.813233@frac.u-strasbg.fr \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).