From: Bastien <bzg@gnu.org>
To: Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: Remove redundant tags of headlines
Date: Fri, 14 Mar 2014 16:28:24 +0100 [thread overview]
Message-ID: <87bnx8re93.fsf@bzg.ath.cx> (raw)
In-Reply-To: <86lhwc4yb3.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 14 Mar 2014 16:03:44 +0100")
Hi Sébastien,
Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:
> ** TODO Project A :FLAGGED:
> *** TODO Task 1 :FLAGGED:
>
> Of course, "FLAGGED" is present in the headline but, at the same time,
> it is inherited.
It means Org favors explicit tags over inherited ones when presenting
them through `org-entry-get'.
> IIUC, the goal of the function written by David was to remove redundant
> tags. In the above case, "FLAGGED" should be removed from "Task 1"
> because it is superfluous (redundant with its parent entry).
Can you find when David's function was still functional for you?
> I'd think that asking for all tags of "Task 1" should output both
> a local "FLAGGED" tag and an inherited "FLAGGED" one.
Well, ALLTAGS means all distinct tags for me, and I don't see how
outputting all duplicate tags would be useful. You'll have to find
another use-case than just David's function to convince me :)
--
Bastien
next prev parent reply other threads:[~2014-03-14 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 15:36 Remove redundant tags of headlines Sebastien Vauban
2014-03-13 15:54 ` Bastien
2014-03-14 11:31 ` Sebastien Vauban
2014-03-14 14:49 ` Bastien
2014-03-14 15:03 ` Sebastien Vauban
2014-03-14 15:28 ` Bastien [this message]
[not found] ` <87bnx8re93.fsf-E3UqQZAQFPqWIDz0JBNUog@public.gmane.org>
2014-03-14 16:17 ` Sebastien Vauban
2014-03-14 12:05 ` Nicolas Richard
2014-03-14 14:53 ` Bastien
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=87bnx8re93.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.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).