From: tumashu <tumashu@163.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-tags-match-list-sublevels is very useful in some condition, why we will semi-obsolete it?
Date: Fri, 22 Mar 2019 10:47:23 +0800 (CST) [thread overview]
Message-ID: <326eded7.5a4c.169a34bbd93.Coremail.tumashu@163.com> (raw)
In-Reply-To: <87k1gsosle.fsf@nicolasgoaziou.fr>
At 2019-03-22 04:55:25, "Nicolas Goaziou" <mail@nicolasgoaziou.fr> wrote:
>Hello,
>
>tumashu <tumashu@163.com> writes:
>
>> (defcustom org-tags-match-list-sublevels t
>> "...
>> This variable is semi-obsolete and probably should always be true. It
>> is better to limit inheritance to certain tags using the variables
>> `org-use-tag-inheritance' and `org-tags-exclude-from-inheritance'."
>>
>> ...
>>
>>
>> "org-tags-match-list-sublevels + search +LEVEL>n " is a very useful tip, if you have many sublevels with many different tags,
>> it can not lost search results nearly, why we will semi-obsolete it?
>
>I do not understand your remark. Could you clarify what you mean? Do you
>have any use case for a nil `org-tags-match-list-sublevels' that cannot
>be handled with tag inheritance?
>
>Thank you.
>
>Regards,
>
>--
>Nicolas Goaziou
I use a refs.org to manage my document, which is like the below example, but have many many headlines.
-------------------------------
* story :story:
** story1
** story2
*** sky :sky:
** story3
*** sky :sky:
** ...
** story100
* sky :sky:
** sky1
*** sky story :story:
** sky2
** sky2
*** sky story :story:
------------------------------
(setq org-tags-match-list-sublevels nil)
I seach "story" info with: "story+LEVEL>1", if I want to know more details, I search "story+LEVEL>2 ... 3 ... 4" with a user-define one key command help.
Sorry for my pool English :-(
prev parent reply other threads:[~2019-03-22 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 14:54 org-tags-match-list-sublevels is very useful in some condition, why we will semi-obsolete it? tumashu
2019-03-21 20:55 ` Nicolas Goaziou
2019-03-22 2:47 ` tumashu [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=326eded7.5a4c.169a34bbd93.Coremail.tumashu@163.com \
--to=tumashu@163.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.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).