zed-industries
Settings to control max tabs open
Check for existing issues
- [X] Completed
Describe the feature
It would be nice to have a setting in zed that allows to configure the max amount tabs that can be open.
Like in IntelliJ products, I typically set my max to 1 so my IDE can only have one tab open at a time that I'm working on. I then use the shortcut for opening recent files to navigate where else I need to if I'm working through multiple files.
Let me know what you guys think. I still have to check if there is already an open issue to allow a shortcut to open recent files.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
I also prefer to work without tabs auto-opening all over the place. A max number would be good, and/or a way to just hide tabs altogether (max of 0 perhaps).
I wanted it really badly, so here's the diff if you want to build your own zed with this integrated: https://github.com/BuonOmo/zed/compare/main...BuonOmo:zed:zentab
I think the footprint is sufficiently light that it could be considered. But I'm doubting that this setting has enough traction...
Some keywords for better finding the issue: zentab (atom ext), tab wrangler (chrome ext), tab limit
This should help with the lsp performance right? In VSCode for example the typescript language server checks the types for all open tabs and setting a low tab limit helps keeping the language server memory usage down
@remorses I could, I'm just not sure there is enough traction for it to be accepted. TBH it is not the only place in this codebase I'd like to contribute whilst not knowing if it is desired by the core team...
I opened a PR with your diff after resolving the conflicts: https://github.com/zed-industries/zed/pull/15926
Let's see if the team agrees on the change
I was waiting for an approval here before making more fuss. But let's see if your way is ok for them! Idk if you cherry-picked the commit, but normally you can ensure the name and information of original committer with git. I'd do it for proper ownership (or make it a pair commit if you intend to squash with your changes)
@remorses and @BuonOmo are there any updates on this? I'd love to help push it across the finish line so we can use this setting asap.
@remainstheday I think the main issue is not the code. I could open a new PR by tomorrow. The issue is the visibility of this, it is unfortunately not a top ranking issue... Maybe if my new PR is clean enough they'll like it even though. Let's say I make it and you review it before them to be sure we're doing good work ? We could even pair up at some point, available today afternoon and tomorrow working hours GMT+1