search

blakedietz / vscode-nested-tags

Stop using your file tree to organize your notes. Transform VSCode into a note-taking app by adding tag support.
MIT License
74 stars 17 forks source link

Feature Request: Option to separate out files list from tags list #58

Open PhilipWhiteside opened 4 years ago

PhilipWhiteside commented 4 years ago

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
PhilipWhiteside commented 4 years ago

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.

tarheels100 commented 3 years ago

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?

blakedietz commented 3 years ago

I would prefer this and from a naive point of view don't see why we couldn't do it.

blakedietz commented 3 years ago

https://github.com/blakedietz/vscode-nested-tags/issues/62