From: ypuntot <ypuntot@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [POLL] Any users setting `org-agenda-use-tag-inheritance' to nil or other non-default value?
Date: Sun, 28 Jan 2024 23:19:17 +0100 (GMT+01:00) [thread overview]
Message-ID: <fd93dbcc-e9bc-4910-a007-e1ba0d819911@gmail.com> (raw)
In-Reply-To: <87il3dqhus.fsf@localhost>
Sorry I didn't get it.
I think it would help too to not overpopulate the agenda, but as I don't use it, I don't vote.
Best
Jan 28, 2024 22:12:39 Ihor Radchenko <yantar92@posteo.net>:
> ypuntot <ypuntot@gmail.com> writes:
>
>> There are several reasons to disable tags inheritance.
>>
>> For example, in project management there could be a tag for a direct responsible for a task, and a different tag for a different direct responsible for a subtask. I could want to see the tasks of the direct responsible, not the subtasks that are already in the hands of a different person.
>> It helps to not overpopulate results.
>
> Indeed. We have `org-use-tag-inheritance' exactly for this purpose - it
> defines tag inheritance globally.
>
> `org-agenda-use-tag-inheritance' is a layer on top that can disable
> `org-use-tag-inheritance' just in agenda.
>
> My question is about `org-agenda-use-tag-inheritance', not about global
> Org settings for tag inheritance.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-01-28 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-28 20:23 [POLL] Any users setting `org-agenda-use-tag-inheritance' to nil or other non-default value? ypuntot
2024-01-28 21:16 ` Ihor Radchenko
2024-01-28 22:19 ` ypuntot [this message]
2024-01-28 22:31 ` Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2024-01-04 15:58 Ihor Radchenko
2024-01-16 18:09 ` Daniel Clemente
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=fd93dbcc-e9bc-4910-a007-e1ba0d819911@gmail.com \
--to=ypuntot@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).