[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] org-tags-match-list-sublevels is very useful in some condition,
From: |
tumashu |
Subject: |
Re: [O] 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) |
At 2019-03-22 04:55:25, "Nicolas Goaziou" <address@hidden> wrote:
>Hello,
>
>tumashu <address@hidden> 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 :-(