Feature Request: Option to separate out files list from tags list
Opened this issue · 4 comments
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.
| Tag List | Editor |
|------------|-------------------------------------------------|
| **Tag1** | **Note 1** |
| Tag2 | Tags: Tag1 |
| Tag2.1 | |
| Tag2.2 | # Title |
| | |
| | Content |
| Notes List | |
|------------| |
| **Note1** | |
| Note2 | |
| Note3 | |
| | |
| | |
| | |
| | |
**=Selected
More flexible layouts is on the VSCode roadmap. When that is implemented it opens up the opportunity to have a 3 paned editor.
| Tag List | Notes List | Editor |
|------------|------------|------------------------------------|
| **Tag1** | **Note1** | **Note 1** |
| Tag2 | Note2 | Tags: Tag1 |
| Tag2.1 | Note3 | |
| Tag2.2 | | # Title |
| | | |
| | | Content |
| | | |
| | | |
| | | |
| | | |
**=Selected
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?
I would prefer this and from a naive point of view don't see why we couldn't do it.