Tabs that group editor grid layouts (Vim-style tabs)
<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Describe the feature you'd like. --> I'm breaking this out into a separate issue from #36700. The discussion in #36700 got a little confusing because of users being sent there from any Vim-style tabs FR #41486, #104483, [VSCodeVim/2989](https://github.com/VSCodeVim/Vim/issues/2989), even though the FR in #36700 is quite different. -------------- Currently, VSCode supports tabs inside of editor groups, where each tab has a one-to-one relationship with a file-- so, effectively, a tab can't really group anything in VSCode. In Vim and some other editors, a tab groups a set of splits. For example (from my own VSCode fork): <img width="1512" alt="image" src="https://user-images.githubusercontent.com/11465187/153884314-2df39d9a-3a93-4521-a000-7c3d8322a707.png"> The key thing to notice here is the **higher-order tab bar on the top**. <img width="548" alt="image" src="https://user-images.githubusercontent.com/11465187/153884609-b5d10063-09a7-479f-83b4-50f9aa7391ea.png"> This lets me group multiple editor groups inside one tab. When I want to think about my parser, I can open the implementation, AST node definitions, and tests **with one click/hotkey** (for me, cmd + 1-9) or fuzzy search of the tab titles. Same thing for my lexer-- impl, grammar, an
Posted by thefakeplace on Feb 14, 2022, 3:39 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
github (E-commerce)
proposal: cmd/cgo: cgo without a C toolchain
Replace PowerToys Run with Command Palette
VPS with a vRack leg
Possibility of Portal 1 Code Inclusion
Introducing NewPlayer
Metrics for PRs are never expiring ("memory leak")
ship even more of the compiler in source form
Flatpak Application TRACKING ISSUE
Tabs that group editor grid layouts (Vim-style tabs)
<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Describe the feature you'd like. --> I'm breaking this out into a separate issue from #36700. The discussion in #36700 got a little confusing because of users being sent there from any Vim-style tabs FR #41486, #104483, [VSCodeVim/2989](https://github.com/VSCodeVim/Vim/issues/2989), even though the FR in #36700 is quite different. -------------- Currently, VSCode supports tabs inside of editor groups, where each tab has a one-to-one relationship with a file-- so, effectively, a tab can't really group anything in VSCode. In Vim and some other editors, a tab groups a set of splits. For example (from my own VSCode fork): <img width="1512" alt="image" src="https://user-images.githubusercontent.com/11465187/153884314-2df39d9a-3a93-4521-a000-7c3d8322a707.png"> The key thing to notice here is the **higher-order tab bar on the top**. <img width="548" alt="image" src="https://user-images.githubusercontent.com/11465187/153884609-b5d10063-09a7-479f-83b4-50f9aa7391ea.png"> This lets me group multiple editor groups inside one tab. When I want to think about my parser, I can open the implementation, AST node definitions, and tests **with one click/hotkey** (for me, cmd + 1-9) or fuzzy search of the tab titles. Same thing for my lexer-- impl, grammar, an
Comments (0)
No comments yet. Start the discussion.