From: Jorge <jorge13515@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bug: typo in [[info:org#Tag hierarchy]] [8.3.4 (8.3.4-34-gacfd41-elpa @ /home/jorge/.emacs.d/elpa/org-20160411/)]
Date: Mon, 11 Apr 2016 15:07:00 -0300 [thread overview]
Message-ID: <CAJR3QneMjQ6uwTTLrDhktNv1NbUic8sxWc_r5oE41kFw3h1tDQ@mail.gmail.com> (raw)
[[info:org#Tag hierarchy]] says:
> Furthermore; The members of a _group tag_ can also be regular
> expression, creating the possibility of more dynamic and rule-based
> tag-structure. The regular expressions in the group must be marked up
> within { }. Example use, to expand on the example given above:
>
> #+TAGS: [ Vision : {V.+} ]
> #+TAGS: [ Goal : {G.+} ]
> #+TAGS: [ AOF : {AOF.+} ]
> #+TAGS: [ Project : {P.+} ]
>
> Searching for the tag `Project' will now list all tags also including
> regular expression matches for `P@.+'. Similar for tag-searches on
> `Vision', `Goal' and `AOF'. This can be good for example if tags for a
> certain project is tagged with a common project-identifier, i.e.
> `P@2014_OrgTags'.
However, the `Project' group tag regex is `P.+', while the first
sentence in the final quoted paragraph cites the regex `P@.+' (with an
`@').
Emacs : GNU Emacs 25.0.92.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.18.6)
of 2016-03-05
Package: Org-mode version 8.3.4 (8.3.4-34-gacfd41-elpa @
/home/jorge/.emacs.d/elpa/org-20160411/)
I run Ubuntu 15.10 with PPAs gnome3-team/gnome3 and gnome3-team/gnome3-staging.
--
- I am Brazilian. I apologize for possibly bad English and I welcome
corrections.
- Please adopt free formats like PDF, ODF, LaTeX, Vorbis, Opus, WebM and 7z.
- Free software for Android: https://f-droid.org/
next reply other threads:[~2016-04-11 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 18:07 Jorge [this message]
2016-04-11 19:33 ` Bug: typo in [[info:org#Tag hierarchy]] [8.3.4 (8.3.4-34-gacfd41-elpa @ /home/jorge/.emacs.d/elpa/org-20160411/)] Nick Dokos
2016-04-12 20:09 ` Nicolas Goaziou
2016-04-13 15:01 ` Nick Dokos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJR3QneMjQ6uwTTLrDhktNv1NbUic8sxWc_r5oE41kFw3h1tDQ@mail.gmail.com \
--to=jorge13515@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.