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: Sat, 19 May 2018 13:53:40 +0200	[thread overview]
Message-ID: <87sh6nhnej.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <23293.25791.381801.813233@frac.u-strasbg.fr> (Alain Cochard's message of "Thu, 17 May 2018 13:17:19 +0200")

Hello,

Alain.Cochard@unistra.fr writes:

> 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.

OK.

> But perhaps it is not pertinent to assume sequential reading.  Or
> perhaps (a digest of) "10 Agenda views" should appear earlier in the
> manual.

I added the variable in the manual, in a footnote, as you suggested.
However, I made the link point to "Agenda Views" because I think this is
a better starting place for all Agenda related questions.

Thank you.

Regards,

-- 
Nicolas Goaziou                                                0x80A93738

      reply	other threads:[~2018-05-19 11:53 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
2018-05-19 11:53     ` Nicolas Goaziou [this message]

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=87sh6nhnej.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
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).