From: Alex Bochannek <alexb@juniper.net>
To: emacs-orgmode@gnu.org
Subject: Agenda and tag inheritance.
Date: Tue, 31 Oct 2006 00:57:33 -0800 [thread overview]
Message-ID: <upsc83ls2.fsf@juniper.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 30 bytes --]
Any comments on this?
Alex.
[-- Attachment #2: Type: message/rfc822, Size: 1252 bytes --]
From: Alex Bochannek <alexb@juniper.net>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Agenda and tag inheritance.
Date: Fri, 13 Oct 2006 22:53:59 -0700
Message-ID: <u7iz3e93c.fsf@juniper.net>
I am wondering about how tag inheritance is supposed to work in
practical terms. I recall that there was some discussion about this in
the past, but I don't think there was resolution.
I use the default setting of org-use-tag-inheritance t and
org-tags-match-list-sublevels nil. That means that if I want to have
something at a sublevel show up in a tag sparse tree, I have to tag it
with the same tag as it's upper level. I am not sure if setting
org-tags-match-list-sublevels would be useful since the sublevels
wouldn't stand out enough.
How about sparse trees with tags on sublevels different from their
inherited tags? I think it would be useful if the levels leading to
the sublevel could also be shown.
Inheritence for todo items doesn't work very well for me. It would be
really nice if the todo agenda view could show the inherited levels
somehow since I end up tagging those items with the tags of their
upper levels as well.
Just some thoughts.
Alex.
[-- Attachment #3: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2006-10-31 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 8:57 Alex Bochannek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-14 5:53 Agenda and tag inheritance Alex Bochannek
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=upsc83ls2.fsf@juniper.net \
--to=alexb@juniper.net \
--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).