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
aticky scroll has become an invaluable way to understand the place of the current syntactical construct in the source hierarchy in the current editor.
I miss it a lot in the explorer tree view for deep workspaces like vscode itself. There are some treadoffs. If the treeview is not high enough, the sticky part would take too much place. With a large enough treeview, the view could bundle dirs.
Suppose the two first lines are sticky :
+ dir
+ | subdir
file1
could be represented giving place for another file in the non sticky part
+ dir / subdir
file1
file2
If more lines are taken by the sticky parts than the non sticky one. Stickiness should be ignored.
The text was updated successfully, but these errors were encountered:
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
aticky scroll has become an invaluable way to understand the place of the current syntactical construct in the source hierarchy in the current editor.
I miss it a lot in the explorer tree view for deep workspaces like vscode itself. There are some treadoffs. If the treeview is not high enough, the sticky part would take too much place. With a large enough treeview, the view could bundle dirs.
Suppose the two first lines are sticky :
could be represented giving place for another file in the non sticky part
If more lines are taken by the sticky parts than the non sticky one. Stickiness should be ignored.
The text was updated successfully, but these errors were encountered: