4 ms·

Thanks for this, I absolutely like it for the most parts. My only complain with Sublime is that if I have 100s of unnamed tabs opened, it gets very difficult t

Thanks for this, I absolutely like it for the most parts. My only complain with Sublime is that if I have 100s of unnamed tabs opened, it gets very difficult to find a particular tab. I wish there was somewhat better tab organisation possible. Maybe there are some plug-ins, I did check last time when I was frustrated with it. Does anyone else face this issue or have I been using it wrong?

chrisan 5y ago
You can use it however you like, but the moment I get to so many tabs open I can't read the titles of all of them is the moment I know I have too many tabs open and just start closing old ones, likely with "close others" action. You have ctrl tab and alt-# but once tab names are no longer visible/readable I don't see the reason to keep so many open. I think the filetree view is exactly how 100s of files should be organized for finding a file you can't remember the name of or ctrl-p for quickly opening a file you do
- Silhouette 5y ago
  You have ctrl tab and alt-# but once tab names are no longer visible/readable I don't see the reason to keep so many open I make extensive use of layouts with several panes, bookmarks and, for longer files, opening multiple views into the same file and code folding. I find these tools particularly helpful when editing or reviewing sets of related files. This happens a lot for me: application code and its tests, front-end and back-end code either side of an API, code defining types/constants/interfaces and code using them, or sometimes larger numbers of related files when these kinds of pairings multiply. As long as everything stays open, ST preserves all of that display context independently for each file/view. Closing and reopening would lose that context every time.
mikeappell 5y ago
I tend to open multiple windows instead. Though, to be fair, I usually do that on a per project basis. I try to close tabs once I realize I'm not going to be using them in the near future. Basically the exact opposite of my browser habits, where I easily have 100 tabs open at any time, lol.

chrisan 5y ago

You can use it however you like, but the moment I get to so many tabs open I can't read the titles of all of them is the moment I know I have too many tabs open and just start closing old ones, likely with "close others" action. You have ctrl tab and alt-# but once tab names are no longer visible/readable I don't see the reason to keep so many open. I think the filetree view is exactly how 100s of files should be organized for finding a file you can't remember the name of or ctrl-p for quickly opening a file you do

Silhouette 5y ago
You have ctrl tab and alt-# but once tab names are no longer visible/readable I don't see the reason to keep so many open I make extensive use of layouts with several panes, bookmarks and, for longer files, opening multiple views into the same file and code folding. I find these tools particularly helpful when editing or reviewing sets of related files. This happens a lot for me: application code and its tests, front-end and back-end code either side of an API, code defining types/constants/interfaces and code using them, or sometimes larger numbers of related files when these kinds of pairings multiply. As long as everything stays open, ST preserves all of that display context independently for each file/view. Closing and reopening would lose that context every time.

mikeappell 5y ago

I tend to open multiple windows instead. Though, to be fair, I usually do that on a per project basis. I try to close tabs once I realize I'm not going to be using them in the near future. Basically the exact opposite of my browser habits, where I easily have 100 tabs open at any time, lol.