From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Julien Cubizolles <j.cubizolles@free.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: tags-todo error with #+FILETAGS: enseignement
Date: Thu, 17 Aug 2017 15:20:53 +0200 [thread overview]
Message-ID: <87ziaypbyi.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <874lt89fi2.fsf@free.fr> (Julien Cubizolles's message of "Wed, 16 Aug 2017 08:46:29 +0200")
Hello,
Julien Cubizolles <j.cubizolles@free.fr> writes:
> When an entry inherits a tag from a #+FILETAGS: line, all its parents
> get matched by a tags-todo agenda, even when they don't have a todo
> keyword.
>
> Consider the following:
>
> (setq org-agenda-files '("/home/wilk/tmp/test-org/test-todo.org"))
> (setq org-agenda-custom-commands
> (quote (
> ("wt" "Boulot"
> (
> (tags-todo "enseignement")
> )
> )
> )))
> (org-agenda)
>
>
> with the following test-todo.org :
>
> #+FILETAGS: enseignement * Contenu ** TODO Cours électrocinétique
>
> The agenda called by "org-agenda w t" displays the "Cours
> électrocinétique" (as it should) but also the "Contenu" even though it
> doesn't have a TODO keyword.
>
> The offending commit is:
>
> commit 942b6267a09e167ad3a546e83205601aa5c0704e
> Author: Nicolas Goaziou <mail@nicolasgoaziou.fr>
> Date: Tue Apr 18 11:55:27 2017 +0200
> org-agenda: `tags-todo' command type includes DONE keywords
Indeed. The solution is not correct. I reverted the commit above.
However, the initial problem the previous patch attempted to fix is
still open. As a consequence, I changed `org-scan-tags' so it also
includes DONE keywords. You can filter these out with "/!" matcher
syntax.
We'll see how it goes.
Thank you.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2017-08-17 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 6:46 tags-todo error with #+FILETAGS: enseignement Julien Cubizolles
2017-08-16 9:46 ` tags-todo error with #+FILETAGS: inheritance Julien Cubizolles
2017-08-17 13:20 ` 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=87ziaypbyi.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=j.cubizolles@free.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).