You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By nesting the files within the tag list the length of the name starts to become limited. I also find it more challenging to keep many tags expanded for jumping between, as the list gets very long so cuts off the bottom, or feels messy and I can't find the tag I want.
This should be optional, as it won't suit everyone. The parsing of content for tags logic should be the same, just splitting at the output/display side of things.
Example
This has been implemented by Markdown-Tags, however that extension seems to be abandoned from its initial upload.
Related to #49 , this would allow for the controlling of what to show, without complexity of handling that in the tag tree directly. Although not the same request exactly #49 takes it one step further on the filtering by tag.
This would effectively cover what I was suggesting, and it even takes it a few steps further (in a good way). I think the implementations that @PhilipWhiteside has suggested would certainly make nested tagging a more convenient feature to use.
@blakedietz, any thoughts on how feasible this would be to implement?
Feature Request
By nesting the files within the tag list the length of the name starts to become limited. I also find it more challenging to keep many tags expanded for jumping between, as the list gets very long so cuts off the bottom, or feels messy and I can't find the tag I want.
This should be optional, as it won't suit everyone. The parsing of content for tags logic should be the same, just splitting at the output/display side of things.
Example
This has been implemented by Markdown-Tags, however that extension seems to be abandoned from its initial upload.
More flexible layouts is on the VSCode roadmap. When that is implemented it opens up the opportunity to have a 3 paned editor.
The text was updated successfully, but these errors were encountered: