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
Would it be possible to add tabs through a custom extension? I quickly looked at the docs but didn't seem possible to add that type of functionality with the current API
Reacted by Karuna Murti, Jody White, Tera, Umed Khudoiberdiev, Misael Taveras, Yuxin Wang, Diego Humpire, Don Shrout, Marat Bektimirov, devochka-valera and 23 more
Yes. But the file remains in the Ctrl+tab context even after closing the file. The experience is not the same as that of Sublime / Atom.
Reacted by Jason Haines, Bharat Patil, John Meyer, Oleksandr Fesenko, Stephan Ahlf, Zhipeng Jiang, Steffen Leistner, Suraj Patil, Travis Illig, Sid Madipalli and 3 more
Snehil Modani (@snehilmodani) right, would it help if the list was showing only what you have in the working files section of the explorer? can you work with the working files list at least?
On a side note: Isn't a layout with file names as tabs more user friendly. It is extensible to having one or more sections of tabs each with their own set of opened files. (Again i am taking Sublime Text as reference here)
I think having tabs or not is independent from having sections. Today you can open up to 3 editors side by side in VS Code and thus we do have sections. Since we do not have tabs, we do not add multiple files into these sections and you can also not have empty sections (which is a separate UX discussion).
Coming back to Ctrl+Tab: We in the team have always worked without tabs from day one and actually we did not even have the working files view for a long time and in fact not so many people in the team are using it. We found that for us it does not matter that much which file you had open or closed. Our minds are rather thinking about the chronological order of which file we edited last. So when I bring up Ctrl+Tab it will typically show me those files I was in last. I am not really looking at the number of files in there, I am only interested in the Top 5 ones at max. The advantage of this model is that you do not have to manage layouts and tabs at all. The management happens naturally while you navigate between files.
We can add a file picker for working files, but it would be interesting to hear if people can be convinced to use Ctrl+Tab as it is today and learn what the issues are.
Reacted by TC Wang, Anthony Nowell, Imre Nagy, Michael Westphal, Anthony Ciccarello, Code Monkey and Juan Ignacio Donoso
Reacted by padpanik, bootstraponline, bstro, Aidin, Sarpdoruk Tahmaz, Garet Claborn and Nicole Orpen
I agree with Ryan Ewen (@RyanEwen). I really appriciate the open development and amount of communication, but these announcements being part of the official "Release Notes" is really confusing.
Maybe this can be split up into actual release notes, and 'what we're working on right now' or something.
Linking this issue in the Roadmap has not been a good idea because if you read it from the first time you will not get a clear idea of the current status ( more than the Milestone). There's still job to be done but the current state is okayish 👍
Yeah, they should summarize issues and then have links to these summaries so people would know the current plan after it was discussed.
Linking to discussions is bad because they tend to be lengthy and people can't get the idea without reading almost everything but dunno maybe it's not possible for them to do it otherwise.
When I started reading the release notes for 1.2, the first thing I looked for was the Tab Feature. I appreciate that they put the current status there. But I also got confused. At first I thought it landed, than I realized it didn't, but a lot of progress was made. In that case it really feels like that item should be at the bottom of the release notes with a link to the discussion or a milestone (they both prove the progress on the feature) along with a small note saying something like "Check out the progress towards Tabs implementation".
Regardless of this minor thing. Great job on the release. VS Code is a great product with amazing development cycle.
Reacted by Eyal, Daniel Ferreira Monteiro Alves and boxinator
Thanks for the feedback on the release notes and sorry for the confusion. I've made modifications to the doc to make it clear the work is not in Stable, but that you can preview the tab work in the Insiders Release.
Having a section towards the end where we talk about work accomplished but not in the stable build is a good idea and we'll do that next month if we have more work that fits into that bucket.
Josh Close (@JoshClose) please open a new issue for this as I will be locking this issue shortly in favor of individual issues instead of this single thread. thx.
Reacted by Ashley Grant, Isaac de Andrade and Eyal
First, let me thank everyone one more time for your thoughts, likes, and dislikes about tabs. The feedback we have seen in this thread (both positive and negative) really shows how passionate people are about the future of VS Code.
I think everyone can agree that we've exhausted the utility of this issue and as a result I am going to lock the conversation. We will leave this issue open until we ship with an option for tabs/no tabs, which we plan to do by the end of the June 2016 iteration.
While the VS Code team may post updates in this issue, you should expect that we will create new issues for additional tab designs or discussions. We will mark issues with the tabs label to make it easier to query. You too can open new tab specific issues and we look forward to your feedback on the specific issues, as together we build the best experiences possible.
#6605 documents all the added or changed command identifiers to use with keybindings. Because the stacks model is such a large change to the UI of VS Code, we decided to revisit all commands that relate to editors or groups.
We are happy to announce that you can now enable tabs in our nightly insider builds (http://code.visualstudio.com/Download#insiders). The related setting is workbench.editor.showTabs. Please refer to our release notes for more details on the concept of editor stacks, preview editors and tabs.
There is still some work planned in this area until the end of the month (and probably beyond) so we are happy to gather feedback from insiders. Feel free to open issues as you find them while using tabs.
tl;dr; enable tabs in VS Code insiders build with workbench.editor.showTabs: true
We are closing for the June milestone during this week with our usual endgame testing. Tabs are on the test plan (#7854) and will get some coverage during the week. We still expect to do fixing on tabs for June and possibly refinements based on feedback post June. The majority of the work is done though, so I will close this issue.
From the description of this work item, Manu Evans (@TurkeyMan) asks for having tabs and a way to move a tab out of the workbench to open inside a new window. I have extracted the latter into #8171 since it is not related to the tabs work we did.
Please continue to file issues on tabs as you see them while trying them out. Thanks for helping in testing the insiders build!
Activity
inakianduaga commentedon Nov 20, 2015
+1
Would it be possible to add tabs through a custom extension? I quickly looked at the docs but didn't seem possible to add that type of functionality with the current API
bpasero commentedon Nov 20, 2015
No, this is currently not possible from an extension (see also http://code.visualstudio.com/docs/extensions/our-approach)
vasumahesh1 commentedon Nov 29, 2015
+1
snehilmodani commentedon Dec 18, 2015
👍
Xety commentedon Dec 21, 2015
👍
Nicte commentedon Dec 21, 2015
+1
Tabs are the default way to work even in Visual Studio, to not mention other text editors such as sublime.
bpasero commentedon Dec 21, 2015
For those that are missing tabs, have you tried using
Ctrl+Tabto navigate in the history of opened files?snehilmodani commentedon Dec 21, 2015
Yes. But the file remains in the
Ctrl+tabcontext even after closing the file. The experience is not the same as that of Sublime / Atom.bpasero commentedon Dec 21, 2015
Snehil Modani (@snehilmodani) right, would it help if the list was showing only what you have in the working files section of the explorer? can you work with the working files list at least?
snehilmodani commentedon Dec 21, 2015
That would be great!
On a side note: Isn't a layout with file names as tabs more user friendly. It is extensible to having one or more sections of tabs each with their own set of opened files. (Again i am taking Sublime Text as reference here)
bpasero commentedon Dec 21, 2015
I think having tabs or not is independent from having sections. Today you can open up to 3 editors side by side in VS Code and thus we do have sections. Since we do not have tabs, we do not add multiple files into these sections and you can also not have empty sections (which is a separate UX discussion).
Coming back to Ctrl+Tab: We in the team have always worked without tabs from day one and actually we did not even have the working files view for a long time and in fact not so many people in the team are using it. We found that for us it does not matter that much which file you had open or closed. Our minds are rather thinking about the chronological order of which file we edited last. So when I bring up Ctrl+Tab it will typically show me those files I was in last. I am not really looking at the number of files in there, I am only interested in the Top 5 ones at max. The advantage of this model is that you do not have to manage layouts and tabs at all. The management happens naturally while you navigate between files.
We can add a file picker for working files, but it would be interesting to hear if people can be convinced to use Ctrl+Tab as it is today and learn what the issues are.
394 remaining items
remcoros commentedon Jun 7, 2016
I agree with Ryan Ewen (@RyanEwen). I really appriciate the open development and amount of communication, but these announcements being part of the official "Release Notes" is really confusing.
Maybe this can be split up into actual release notes, and 'what we're working on right now' or something.
javmonisu commentedon Jun 7, 2016
Linking this issue in the Roadmap has not been a good idea because if you read it from the first time you will not get a clear idea of the current status ( more than the Milestone). There's still job to be done but the current state is okayish 👍
soyeyalon commentedon Jun 7, 2016
Yeah, they should summarize issues and then have links to these summaries so people would know the current plan after it was discussed.
Linking to discussions is bad because they tend to be lengthy and people can't get the idea without reading almost everything but dunno maybe it's not possible for them to do it otherwise.
andradei commentedon Jun 7, 2016
When I started reading the release notes for 1.2, the first thing I looked for was the Tab Feature. I appreciate that they put the current status there. But I also got confused. At first I thought it landed, than I realized it didn't, but a lot of progress was made. In that case it really feels like that item should be at the bottom of the release notes with a link to the discussion or a milestone (they both prove the progress on the feature) along with a small note saying something like "Check out the progress towards Tabs implementation".
Regardless of this minor thing. Great job on the release. VS Code is a great product with amazing development cycle.
JoshClose commentedon Jun 7, 2016
VSCode just updated to 1.3.0-insider. Recent files seems to be gone. Is there a way to do that now?
chrisdias commentedon Jun 7, 2016
Thanks for the feedback on the release notes and sorry for the confusion. I've made modifications to the doc to make it clear the work is not in Stable, but that you can preview the tab work in the Insiders Release.
Having a section towards the end where we talk about work accomplished but not in the stable build is a good idea and we'll do that next month if we have more work that fits into that bucket.
chrisdias commentedon Jun 7, 2016
Josh Close (@JoshClose) please open a new issue for this as I will be locking this issue shortly in favor of individual issues instead of this single thread. thx.
chrisdias commentedon Jun 7, 2016
First, let me thank everyone one more time for your thoughts, likes, and dislikes about tabs. The feedback we have seen in this thread (both positive and negative) really shows how passionate people are about the future of VS Code.
I think everyone can agree that we've exhausted the utility of this issue and as a result I am going to lock the conversation. We will leave this issue open until we ship with an option for tabs/no tabs, which we plan to do by the end of the June 2016 iteration.
While the VS Code team may post updates in this issue, you should expect that we will create new issues for additional tab designs or discussions. We will mark issues with the
tabslabel to make it easier to query. You too can open new tab specific issues and we look forward to your feedback on the specific issues, as together we build the best experiences possible.Thanks again, now go and install the Insiders Release!
bpasero commentedon Jun 9, 2016
#6605 documents all the added or changed command identifiers to use with keybindings. Because the stacks model is such a large change to the UI of VS Code, we decided to revisit all commands that relate to editors or groups.
bpasero commentedon Jun 19, 2016
We are happy to announce that you can now enable tabs in our nightly insider builds (http://code.visualstudio.com/Download#insiders). The related setting is
workbench.editor.showTabs. Please refer to our release notes for more details on the concept of editor stacks, preview editors and tabs.There is still some work planned in this area until the end of the month (and probably beyond) so we are happy to gather feedback from insiders. Feel free to open issues as you find them while using tabs.
Thanks!
stevencl commentedon Jun 21, 2016
As Benjamin Pasero (@bpasero) has mentioned you can now enable tabs in our nightly insider builds.
If you have tried this and can spare 30 minutes to share your feedback, please sign up for a chat here: https://calendly.com/stevencl/vs-code-tabs/
Unfortunately I can only offer time slots during the day my time (I am in Edinburgh, Scotland) Monday and Tuesday next week.
bpasero commentedon Jun 27, 2016
tl;dr; enable tabs in VS Code insiders build with
workbench.editor.showTabs: trueWe are closing for the June milestone during this week with our usual endgame testing. Tabs are on the test plan (#7854) and will get some coverage during the week. We still expect to do fixing on tabs for June and possibly refinements based on feedback post June. The majority of the work is done though, so I will close this issue.
From the description of this work item, Manu Evans (@TurkeyMan) asks for having tabs and a way to move a tab out of the workbench to open inside a new window. I have extracted the latter into #8171 since it is not related to the tabs work we did.
Please continue to file issues on tabs as you see them while trying them out. Thanks for helping in testing the insiders build!