Open liangzh-404 opened 2 years ago
Thank you! I'll check the behavior. (That don't be expected)
I tested in some cases, don't you have the tree like this?
a | b | | c | | | d | | | | e | d | | e | | | a | | | | b | | | | | c
If you don't use a/b/c
and d/e
together in one note, the tree will be separated.
This nested level feature is for cases that use relevant tags. (i.e., blog/2022/03
and status/draft
.)
Expand Limit
will help you, did you try it?
Or, do you want to use this feature in nested tags only?
I find that you use a diffrent symbol to differentiate "relevant tag" and "inherit tag", right now it's enough for me. But I do think it will be better to provide option to not show relevant tag, sometimes I found out it made the path too long~
This nested level feature is for cases that use relevant tags. (i.e.,
blog/2022/03
andstatus/draft
.)Expand Limit
will help you, did you try it? Or, do you want to use this feature in nested tags only?
@vrtmrz Thanks for making this useful plugin! But there are some not comfortable place.
My case: I will use several tags in one file. And all tags are have its nested.
For example:
category/A/AA/AAA
, category/A/AA/AAB
, ...
filetype/A
, filetype/B
, ...
...
So when I want to use category tag as folder view, the file in the category will continually separate by other nested tags, which is not I expected.
The option Expand Limit
not work well. Because the limit level only count current nested tag. Other nested tags are not under controll and still can click into it continually.
Is it possible to set a option like "Nested tag folder only shows tags under current nest, ignore other tags"?
Thank you for asking me! This plugin was initially made for finding tagged notes. Now also we can organise notes, but there are lingering, here and there.
Actually, this behaviour is almost useless or disturbing, but sometimes incredibly useful.
If it is bothersome, could you please try to enable the feature Reduce duplicated parents in nested tags
?
Suppose I have note with tags "a/b/c, d/e", now the folder list will be like : a | b | | c | | | d | | | | e but I think maybe it will make more sense to bahave like the below one? After all, usually d/e and a/b/c is not relevant a | b | | c d | e