Add support for tab tearoff and tab merge #1675

@cdmihai commented on GitHub (Sep 25, 2019):

This would be so useful. I constantly open new tabs on some focused work, start splitting panes within the tab, and then at some point decide to move the whole tab and panes (right now I just recreate the panes and their directories from scratch) to a new terminal window in a new virtual desktop.

@cdmihai commented on GitHub (Sep 25, 2019): This would be so useful. I constantly open new tabs on some focused work, start splitting panes within the tab, and then at some point decide to move the whole tab and panes (right now I just recreate the panes and their directories from scratch) to a new terminal window in a new virtual desktop.

claunia commented

@adgustaf commented on GitHub (Mar 23, 2020):

Hi,

Any progress on this? Just wanted to say I find this to be very useful.

Thanks for all your hard work on this product!

@adgustaf commented on GitHub (Mar 23, 2020): Hi, Any progress on this? Just wanted to say I find this to be very useful. Thanks for all your hard work on this product!

claunia commented

@DHowett-MSFT commented on GitHub (Mar 23, 2020):

Thanks for asking! Unfortunately, there hasn’t been any progress. When there is, this issue will be the first to be updated about it.

@DHowett-MSFT commented on GitHub (Mar 23, 2020): Thanks for asking! Unfortunately, there hasn’t been any progress. When there is, this issue will be the first to be updated about it.

claunia commented

@adgustaf commented on GitHub (Mar 23, 2020):

Thanks for the info! Okay I'll be following this issue :)

@adgustaf commented on GitHub (Mar 23, 2020): Thanks for the info! Okay I'll be following this issue :)

claunia commented

@pcgeek86 commented on GitHub (Nov 21, 2020):

I just tried to tear a tab off a window in the Windows Terminal Preview version and was unable to. That led me to searching for this issue.

Here's my use case: I am trying to demonstrate connecting two separate tmux clients to the same session, and running at different window sizes. In order to effectively do this, I need to resize one tmux window to separate dimensions from the other one. Since both my Ubuntu WSL tabs were running in the same Windows Terminal window, I was unable to do this. Hence, I tried to "tear" one of the existing tabs off into its own Windows 10 window.

This is where I got stuck, and had to open a brand new Terminal window instead, and then open up an Ubuntu tab in that window.

The work-around isn't hard, but it's just convenient to be able to tear off existing tabs, just like you can in Google Chrome.

@pcgeek86 commented on GitHub (Nov 21, 2020): I just tried to tear a tab off a window in the Windows Terminal Preview version and was unable to. That led me to searching for this issue. Here's my use case: I am trying to demonstrate connecting two separate tmux clients to the same session, and running at different window sizes. In order to effectively do this, I need to resize one tmux window to separate dimensions from the other one. Since both my Ubuntu WSL tabs were running in the same Windows Terminal window, I was unable to do this. Hence, I tried to "tear" one of the existing tabs off into its own Windows 10 window. This is where I got stuck, and had to open a brand new Terminal window instead, and then open up an Ubuntu tab in that window. The work-around isn't hard, but it's just convenient to be able to tear off existing tabs, just like you can in Google Chrome.

claunia commented

@xairoo commented on GitHub (Jan 25, 2021):

Moving tabs to a different window is important.

I never use Edge, I am a Firefox fan boy (privacy, sharp fonts, amazing dev tools and so on ;-)). But I just tested to move a tab to a different Edge window. It works! Well guys, I am sure you can handle this for Windows Terminal too! =)

@xairoo commented on GitHub (Jan 25, 2021): Moving tabs to a different window is important. I never use Edge, I am a Firefox fan boy (privacy, sharp fonts, amazing dev tools and so on ;-)). But I just tested to move a tab to a different Edge window. It works! Well guys, I am sure you can handle this for Windows Terminal too! =)

claunia commented

@flipbit03 commented on GitHub (Feb 5, 2021):

I need this so much.

@flipbit03 commented on GitHub (Feb 5, 2021): I need this so much.

claunia commented

@opticyclic commented on GitHub (Feb 15, 2021):

Tab tearoff works with Konsole and web browsers which is why I expected this to work.

Interestingly, when I tried it out with other multi-tabbed applications(e.g. Kate) it didn't do it as I expected.

Regardless, it would be useful to drag out tabs to different windows to help organise processes.

@opticyclic commented on GitHub (Feb 15, 2021): Tab tearoff works with Konsole and web browsers which is why I expected this to work. Interestingly, when I tried it out with other multi-tabbed applications(e.g. Kate) it didn't do it as I expected. Regardless, it would be useful to drag out tabs to different windows to help organise processes.

claunia commented

@andgeno commented on GitHub (Feb 27, 2021):

Yes, this is an important feature. Please add support. Thanks! 😄

@andgeno commented on GitHub (Feb 27, 2021): Yes, this is an important feature. Please add support. Thanks! 😄

claunia commented

@eriksneff commented on GitHub (May 5, 2021):

I'm curious how many people are subscribed to this thread. Browsers have trained us all how tabs work, and it's really unexpected when a tool like Windows Terminal has tabs but doesn't behave like browsers do. Actually, given this is almost 2 years old, there's also a layer of sadness I and I'm guessing many others feel to see a table stakes feature like this be deprioritized this long.

@eriksneff commented on GitHub (May 5, 2021): I'm curious how many people are subscribed to this thread. Browsers have trained us all how tabs work, and it's really unexpected when a tool like Windows Terminal has tabs but doesn't behave like browsers do. Actually, given this is almost 2 years old, there's also a layer of sadness I and I'm guessing many others feel to see a table stakes feature like this be deprioritized this long.

claunia commented

@zadjii-msft commented on GitHub (May 5, 2021):

Listen here pal. This hasn't been deprioritized, this has literally been my main priority for the last basically 12 months now. I've been researching. I've been prototyping. I've been writing specs. There has been a lot of planning that's gone into this, to make sure it works, and works for all the different scenarios we have in mind in the Terminal. Now that we've got a lot of the other foundations out of the way, I'm finally starting to get close to landing this. So I'd appreciate your continued patience while we work on this.

As always, we'll post here when there's an update to share.

@zadjii-msft commented on GitHub (May 5, 2021): Listen here pal. This hasn't been deprioritized, this has literally been my main priority for the last basically 12 months now. [I've been researching](https://github.com/microsoft/terminal/issues/5000). [I've been prototyping](https://github.com/microsoft/terminal/branches/all?query=oop). [I've been writing specs](https://github.com/microsoft/terminal/tree/main/doc/specs/%235000%20-%20Process%20Model%202.0). There has been a lot of planning that's gone into this, to make sure it works, and works for all the different scenarios we have in mind in the Terminal. Now that we've got a lot of the other foundations out of the way, I'm finally starting to [get close to landing this](https://github.com/microsoft/terminal/tree/dev/migrie/oop/the-whole-thing). So I'd appreciate your continued patience while we work on this. As always, we'll post here when there's an update to share.

claunia commented

@dailytabs commented on GitHub (Jun 2, 2021):

"Listen here pal." wow, how condescending. I noticed I had an unknown prejudice against this guy, so looked around for more comments to better inform myself and hopefully change my mind and this is the first one I saw. No need to look further. Holy shit, dude. Get a grip! I may be toxic myself at times (ok, most of the time), but I'm a user. You are a project member and, apparent, MS employee. Just, wow! Take a course on community management or get out of the public eye.

@dailytabs commented on GitHub (Jun 2, 2021): "Listen here pal." wow, how condescending. I noticed I had an unknown prejudice against this guy, so looked around for more comments to better inform myself and hopefully change my mind and this is the first one I saw. No need to look further. Holy shit, dude. Get a grip! I may be toxic myself at times (ok, most of the time), but I'm a user. You are a project member and, apparent, MS employee. Just, wow! Take a course on community management or get out of the public eye.

claunia commented

@DHowett commented on GitHub (Jun 2, 2021):

I appreciate that the original comment was worded more strongly and that it may have been a bad day/week for both/either Mike or Erik. I'm also locking this because I want to keep it on-topic -- not to suppress discussion, but because these discussions are never fruitful.

@DHowett commented on GitHub (Jun 2, 2021): I appreciate that the original comment was worded more strongly and that it may have been a bad day/week for both/either Mike or Erik. I'm also locking this because I want to keep it on-topic -- not to suppress discussion, but because these discussions are never fruitful.

claunia commented

@kczx3 commented on GitHub (Oct 11, 2021):

@zadjii-msft Would you be able to provide a brief update of the progress towards these features? I can see there's definitely been activity and commits where this issue has been referenced but a nice couple sentence paragraph of your progress would be very uplifting. Thanks for your time!

@kczx3 commented on GitHub (Oct 11, 2021): @zadjii-msft Would you be able to provide a brief update of the progress towards these features? I can see there's definitely been activity and commits where this issue has been referenced but a nice couple sentence paragraph of your progress would be very uplifting. Thanks for your time!

claunia commented

@zadjii-msft commented on GitHub (Oct 12, 2021):

More specific details, including my todo list are in #5000. I'm hoping to do the control settings rewrite this release (dev/migrie/oop/ragnarok), and hopefully some of the other foundation work before the end of the year (dev/migrie/oop/infinity-war). Hopefully we can get "move-pane -w <id> to move a pane/tab to another Terminal window" early next year, and followed shortly by tearing actual tabs out. This is still my main priority, just one that keeps getting sidelined by other things that can ship in a single release cycle. We've got the end of the year coming up and things always slow way down around then, and there's some time dedicated in the near future to improving our tooling (which should help accelerate overall code velocity)

@zadjii-msft commented on GitHub (Oct 12, 2021): More specific details, including my todo list are in #5000. I'm hoping to do the control settings rewrite this release (`dev/migrie/oop/ragnarok`), and hopefully some of the other foundation work before the end of the year (`dev/migrie/oop/infinity-war`). Hopefully we can get "`move-pane -w <id>` to move a pane/tab to another Terminal window" early next year, and followed shortly by tearing actual tabs out. This is still my main priority, just one that keeps getting sidelined by other things that can ship in a single release cycle. We've got the end of the year coming up and things always slow way down around then, and there's some time dedicated in the near future to improving our tooling (which should help accelerate overall code velocity)

claunia commented

@patrikhuber commented on GitHub (Mar 12, 2022):

I just tried to drag a tab from one WT to another, fully expecting it to work. And I ended up here! :-) Another big thumbs up from me for this feature, looking forward to it, it will be really useful.

@patrikhuber commented on GitHub (Mar 12, 2022): I just tried to drag a tab from one WT to another, fully expecting it to work. And I ended up here! :-) Another big thumbs up from me for this feature, looking forward to it, it will be really useful.

claunia commented

@lipanpan-hub commented on GitHub (Apr 1, 2022):

期待这个功能的进展

@lipanpan-hub commented on GitHub (Apr 1, 2022): 期待这个功能的进展

claunia commented

@MattBDev commented on GitHub (May 10, 2022):

I hope that this feature will not be limited to Windows 11 and will be backwards compatible with Windows 10. A lot of businesses and users are still on Windows 10 and likely will be for the time being.

@MattBDev commented on GitHub (May 10, 2022): I hope that this feature will not be limited to Windows 11 and will be backwards compatible with Windows 10. A lot of businesses and users are still on Windows 10 and likely will be for the time being.

claunia commented

@zadjii-msft commented on GitHub (May 11, 2022):

@MattBDev Don't worry, no part of how I plan on implementing tearoff is restricted to Windows 11. Something quite dramatic would have to come up in the next couple months to change that.

@zadjii-msft commented on GitHub (May 11, 2022): @MattBDev Don't worry, no part of how I plan on implementing tearoff is restricted to Windows 11. Something quite dramatic would have to come up in the next couple months to change that.

claunia commented

@paulbrzeski commented on GitHub (Aug 2, 2022):

Still waiting for this feature in August 2022...

@paulbrzeski commented on GitHub (Aug 2, 2022): Still waiting for this feature in August 2022...

claunia commented

@eriksneff commented on GitHub (Aug 2, 2022):

My thoughts exactly...

@eriksneff commented on GitHub (Aug 2, 2022): My thoughts exactly...

claunia commented

@zadjii-msft commented on GitHub (Aug 2, 2022):

This is literally being actively worked on. See https://github.com/microsoft/terminal/issues/5000#issuecomment-1185447944 for the latest status update.

@zadjii-msft commented on GitHub (Aug 2, 2022): This is literally being actively worked on. See https://github.com/microsoft/terminal/issues/5000#issuecomment-1185447944 for the latest status update.

claunia commented

@eriksneff commented on GitHub (Aug 3, 2022):

You literally just marked my honest opinion as spam. WTF

@eriksneff commented on GitHub (Aug 3, 2022): You literally just marked my honest opinion as spam. WTF

claunia commented

@eriksneff commented on GitHub (Aug 3, 2022):

This issue was opened 3 years ago. I think community upset over it is
justified, and marking that organic discourse as spam is at best flat our
wrong, and at worst indicative of a seriously dysfunctional corporate
culture at microsoft.

@eriksneff commented on GitHub (Aug 3, 2022): This issue was opened 3 years ago. I think community upset over it is justified, and marking that organic discourse as spam is at best flat our wrong, and at worst indicative of a seriously dysfunctional corporate culture at microsoft.

claunia commented

@zadjii-msft commented on GitHub (Aug 3, 2022):

I collapsed the comments because they did not constructively contribute to the conversation at hand. If you'd like to +1 a comment or issue, the best way to do that is to just press the 👍 button. I'm pretty liberal throughout the repo of collapsing any comments that don't constructively contribute to the discussion, especially on a thread with 300 upvotes. Commentary on how we run this repo is probably best directed at a separate discussion rather than in the midst of another thread.

Progress has been made consistently on tab tear out over the last few years (as linked in the broader thread). It's involved multiple huge refactors of the codebase, so it's taken quite some effort. There are also other priorities that have come up, and with our limited engineering resources, we choose to provide consistent feature enhancements to the product rather than lock everything down for a few months to finish this one feature.

The work I've got in the last few branches is very promising, but it needs a lot of polish before we can ship it. If anyone's got any advice or wants to help contribute - the comments at the bottom of #5000 have links to the work in progress, and what still needs to be done. Thanks!

@zadjii-msft commented on GitHub (Aug 3, 2022): I collapsed the comments because they did not constructively contribute to the conversation at hand. If you'd like to +1 a comment or issue, the best way to do that is to just press the 👍 button. I'm pretty liberal throughout the repo of collapsing any comments that don't constructively contribute to the discussion, especially on a thread with 300 upvotes. Commentary on how we run this repo is probably best directed at a [separate discussion](https://github.com/microsoft/terminal/discussions) rather than in the midst of another thread. Progress has been made consistently on tab tear out over the last few years (as linked in the broader thread). It's involved multiple huge refactors of the codebase, so it's taken quite some effort. There are also other priorities that have come up, and with our limited engineering resources, we choose to provide consistent feature enhancements to the product rather than lock everything down for a few months to finish this one feature. The work I've got in the last few branches is very promising, but it needs a lot of polish before we can ship it. If anyone's got any advice or wants to help contribute - the comments at the bottom of #5000 have links to the work in progress, and what still needs to be done. Thanks!

claunia commented

@Volt-Xoccula commented on GitHub (Aug 19, 2022):

I am just adding another comment to the fire instead of an issue request.. Make the windows able to be torn off. This is a BASIC function of any tabbed interface. It is the core of a tabbed interface.

The entire predicate of a tabbed interface comes from Microdot's prior unwillingness to provide native support for group windows. Now in this implementation of a Microsoft product, the opposite is true.
Why you would utilized a common interface feature and then not implement the actual reason why that feature exists is completely bizarre.

Perhaps the most bizarre about this is that you mention in the original feature request from 3 years ago that this is a multi-instance application. It still is, and it still should be. This aids troubleshooting efforts and minimizes the effort to implement an core function and usability in line with standard UX design recommendations..
The application core functions exactly the same as if you have two open windows or one with two tabs. You nest and run the subordinate shells within the app-x parent thread no matter what.... Every tabbed UX application does this.

Honestly take a step back and look at it from a 1000' view. You are currently working on the function and UX of the most critical application for systems administrators for the bulk of your business. Have you ever tried to identify the root cause of a mail issue with a hybrid deployment of azure and on-prem exchange? It,s not unusual to have 4 screens open at once actively gathering or displaying information.

This issue should be prioritized and there shouldn't be a complaint about it. This team made the decision to revolutionize the method thhat people utilize the Windows shell. For some reason you only read half the book on a UX design. Imagine if Microsoft Launched te chromium version of Edge and didn't implement tear off tabs. How would the general reception of that product go?

@Volt-Xoccula commented on GitHub (Aug 19, 2022): I am just adding another comment to the fire instead of an issue request.. Make the windows able to be torn off. This is a BASIC function of any tabbed interface. It is the core of a tabbed interface. The entire predicate of a tabbed interface comes from Microdot's prior unwillingness to provide native support for group windows. Now in this implementation of a Microsoft product, the opposite is true. Why you would utilized a common interface feature and then not implement the actual reason why that feature exists is completely bizarre. Perhaps the most bizarre about this is that you mention in the original feature request _from 3 years ago_ that this is a multi-instance application. It still is, and it still should be. This aids troubleshooting efforts and minimizes the effort to implement an core function and usability in line with **standard** UX design recommendations.. The application core functions exactly the same as if you have two open windows or one with two tabs. You nest and run the subordinate shells within the app-x parent thread no matter what.... Every tabbed UX application does this. Honestly take a step back and look at it from a 1000' view. You are currently working on the function and UX of the most critical application for systems administrators for the bulk of your business. Have you ever tried to identify the root cause of a mail issue with a hybrid deployment of azure and on-prem exchange? It,s not unusual to have 4 screens open at once actively gathering or displaying information. This issue should be prioritized and there shouldn't be a complaint about it. This team made the decision to revolutionize the method thhat people utilize the Windows shell. For some reason you only read half the book on a UX design. Imagine if Microsoft Launched te chromium version of Edge and didn't implement tear off tabs. How would the general reception of that product go?

claunia commented

@DHowett commented on GitHub (Aug 20, 2022):

Thanks for your input.

This issue is well understood and additional community commentary on it has not provided an equivalent amount of additional clarity.

I'm going to lock it for now. If there is additional insight you can provide, I'd love to receive it in a thread that will not notify upwards of twenty people and an unknown number of additional subscribers.

@DHowett commented on GitHub (Aug 20, 2022): Thanks for your input. This issue is well understood and additional community commentary on it has not provided an equivalent amount of additional clarity. I'm going to lock it for now. If there is additional insight you can provide, I'd love to receive it in a thread that will _not_ notify upwards of twenty people and an unknown number of additional subscribers.

claunia commented

@saschanaz commented on GitHub (Mar 30, 2023):

Amazing, thank you for all the effort for such a long time and congrats for finally landing it! 🎉🎉

@saschanaz commented on GitHub (Mar 30, 2023): Amazing, thank you for all the effort for such a long time and congrats for finally landing it! 🎉🎉

claunia commented

@Korb commented on GitHub (Apr 6, 2023):

Is it supposed to add the "Move Tab to New Window" item to the context menu of the tabs

like Mozilla Firefox

in the context of this task?

Screenshots of Windows Terminal Preview 1.17.1023 and Mozilla Firefox 111.0.1 (64-bit), Microsoft Windows 10.0.19045.2788.

@Korb commented on GitHub (Apr 6, 2023): Is it supposed to add the "Move Tab to New Window" item to the context menu of the tabs ![Screenshot_2023-04-06_08-54-54](https://user-images.githubusercontent.com/3509797/230285656-909af440-5b8a-4d98-91cd-e72b8d4feaf4.png) like Mozilla Firefox ![Screenshot_2023-04-06_08-55-44](https://user-images.githubusercontent.com/3509797/230285863-db1a8f4d-f1ca-44b5-96d3-eca158e30f37.png) in the context of this task? Screenshots of Windows Terminal Preview 1.17.1023 and Mozilla Firefox 111.0.1 (64-bit), Microsoft Windows 10.0.19045.2788.

claunia commented

@zadjii-msft commented on GitHub (Apr 6, 2023):

@Korb I haven't added that yet but I'll track that in #15127

@zadjii-msft commented on GitHub (Apr 6, 2023): @Korb I haven't added that yet but I'll track that in #15127

claunia commented

@zadjii-msft commented on GitHub (Apr 23, 2023):

@TylerHelt0 Thanks for your interest in this issue! If you'd read, you'll see that this was merged a couple weeks ago, in #14901

@zadjii-msft commented on GitHub (Apr 23, 2023): @TylerHelt0 Thanks for your interest in this issue! If you'd read, you'll see that this was merged a couple weeks ago, in #14901 ![image](https://user-images.githubusercontent.com/18356694/233840675-c1dd68c3-685c-4483-9caa-2a1b5b6537a4.png)

claunia commented

@WeihanLi commented on GitHub (Apr 23, 2023):

Is there a release plan for this

@WeihanLi commented on GitHub (Apr 23, 2023): Is there a release plan for this

claunia commented

@zadjii-msft commented on GitHub (Apr 24, 2023):

Is there a release plan for this

We'll release it when it is ready 😜. I'm tracking the release blockers for tear-out specifically over in #14957. There's assorted other release blockers for 1.18 around the repo as well. There have been quite a few ENORMOUS changes to the codebase in 1.18, so bear with us while we make sure that it's in a stable place for release ☺️

@zadjii-msft commented on GitHub (Apr 24, 2023): > Is there a release plan for this We'll release it when it is ready 😜. I'm tracking the release blockers for tear-out specifically over in #14957. There's assorted other release blockers for 1.18 around the repo as well. There have been quite a few ENORMOUS changes to the codebase in 1.18, so bear with us while we make sure that it's in a stable place for release ☺️

claunia commented

@malaclypse commented on GitHub (Sep 19, 2023):

Any plans to release this soon?

@malaclypse commented on GitHub (Sep 19, 2023): Any plans to release this soon?

claunia commented

@zadjii-msft commented on GitHub (Sep 19, 2023):

This was released 4 months ago: https://github.com/microsoft/terminal/releases/tag/v1.18.1421.0

Though, unclear why the bot didn't make it's rounds to post in this thread...

:tada:This issue was addressed in #14901, which has now been successfully released as Windows Terminal Preview v1.18.1421.0.🎉

Handy links:

</🤖>

@zadjii-msft commented on GitHub (Sep 19, 2023): This was released 4 months ago: https://github.com/microsoft/terminal/releases/tag/v1.18.1421.0 Though, unclear why the bot didn't make it's rounds to post in this thread... \<bot hat> :tada:This issue was addressed in #14901, which has now been successfully released as `Windows Terminal Preview v1.18.1421.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.18.1421.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge) \</🤖>

claunia commented

@kczx3 commented on GitHub (Sep 20, 2023):

"released" is a stretch I'd say since 1.18 has been in pre-release since May 23rd... Is there something specific holding 1.18 back and causing you to miss your quarterly releases?

@kczx3 commented on GitHub (Sep 20, 2023): "released" is a stretch I'd say since 1.18 has been in pre-release since May 23rd... Is there something specific holding 1.18 back and causing you to miss your quarterly releases?

claunia commented

@zadjii-msft commented on GitHub (Sep 20, 2023):

Preview releases are still solid releases. Honestly, that's what I consider the main Terminal releases. 1.18 is held back from Stable for namely #15496, but also to line up 1.19 with some other internal work/announcements/etc.

Also, we're on a roughly quarterly schedule. "Roughly" doing a lot of work here. I'd much rather land a solid release after a 1mo delay, than cut early for the sake of releasing every 3mos.

@zadjii-msft commented on GitHub (Sep 20, 2023): Preview releases are still solid releases. Honestly, that's what I consider the main Terminal releases. 1.18 is held back from Stable for namely #15496, but also to line up 1.19 with some other internal work/announcements/etc. Also, we're on a **roughly** quarterly schedule. "Roughly" doing a lot of work here. I'd much rather land a solid release after a 1mo delay, than cut early for the sake of releasing every 3mos.

claunia commented

@kczx3 commented on GitHub (Sep 20, 2023):

No one is trying to downplay the amount of work you're doing on this. We all agree this is a hefty project.

I think we could probably argue back and forth all day about calling preview releases the main release. I'm comfortable sitting tight until it reaches general availability and out of a preview or dev release.

@kczx3 commented on GitHub (Sep 20, 2023): No one is trying to downplay the amount of work you're doing on this. We all agree this is a hefty project. I think we could probably argue back and forth all day about calling preview releases the main release. I'm comfortable sitting tight until it reaches general availability and out of a preview or dev release.

claunia commented

@randomascii commented on GitHub (Sep 21, 2023):

I don't think we're pushing you to release faster (I'm not, anyway). But I think that it would be less confusing if you didn't say "this was released 4 months ago" when it was only released to the preview channel.

I am probably not alone in not using the preview channel. I'm sure it's fairly stable, but I've got enough variables in my life so I am using the release channel, so for my purposes it is not yet released.

In other words, it would have been clearer to me if you had said "This was released to the preview channel 4 months ago..." and perhaps an estimate of when it would be released to the, well, release channel.

@randomascii commented on GitHub (Sep 21, 2023): I don't think we're pushing you to release faster (I'm not, anyway). But I think that it would be less confusing if you didn't say "this was released 4 months ago" when it was only released to the preview channel. I am probably not alone in not using the preview channel. I'm sure it's fairly stable, but I've got enough variables in my life so I am using the release channel, so for my purposes it is not yet released. In other words, it would have been clearer to me if you had said "This was released to the preview channel 4 months ago..." and perhaps an estimate of when it would be released to the, well, _release_ channel.

claunia commented

2026-01-30 22:33:34 +00:00

@kczx3 commented on GitHub (Sep 21, 2023):

@randomascii
Thank you for saying what I was trying to in a much better way.

@kczx3 commented on GitHub (Sep 21, 2023): @randomascii Thank you for saying what I was trying to in a much better way.

claunia commented

@EduardDurech commented on GitHub (Nov 18, 2023):

Sorry if this has already been noted, there are many hidden comments and did not see it already mentioned

While tab tear-off works in non-elevated Terminal, it doesn't seem to work with elevated Administrative privileges. I'm assuming this would require a new User Account Control prompt

V 1.18.2822.0

@EduardDurech commented on GitHub (Nov 18, 2023): Sorry if this has already been noted, there are many hidden comments and did not see it already mentioned While tab tear-off works in non-elevated Terminal, it doesn't seem to work with elevated Administrative privileges. I'm assuming this would require a new User Account Control prompt V 1.18.2822.0

claunia commented

2026-01-30 22:33:34 +00:00

@zadjii-msft commented on GitHub (Nov 20, 2023):

@EduardDurech There's a lot more details about the admin drag/drop problem over in #6661.

@zadjii-msft commented on GitHub (Nov 20, 2023): @EduardDurech There's a lot more details about the admin drag/drop problem over in #6661.

claunia commented

@patricknelson commented on GitHub (Nov 20, 2023):

Seeing this in stable and it's awesome, thanks @zadjii-msft! It's great to see a conclusion to "the penultimate chapter in the saga of tear-out!" 😄 With all the unnecessary anger and frustration I've seen you guys get, I figured a bit of appreciation is in order. Thanks for getting this across the finish line! 🎉

@patricknelson commented on GitHub (Nov 20, 2023): Seeing this in stable and it's awesome, thanks @zadjii-msft! It's great to see a conclusion to "the penultimate chapter in the saga of tear-out!" 😄 With all the unnecessary anger and frustration I've seen you guys get, I figured a bit of appreciation is in order. Thanks for getting this across the finish line! 🎉

claunia commented

@biggestsonicfan commented on GitHub (Mar 22, 2024):

Took quite a long time to figure out I had to drag a tab in-between two other tabs to get it to move to a different window and not at the end of other tabs.

@biggestsonicfan commented on GitHub (Mar 22, 2024): Took quite a long time to figure out I had to drag a tab in-between two other tabs to get it to move to a different window and not at the end of other tabs.

claunia commented

@Gravifer commented on GitHub (Mar 23, 2024):

seems like a mishandled corner case? @zadjii-msft

Took quite a long time to figure out I had to drag a tab in-between two other tabs to get it to move to a different window and not at the end of other tabs.

@Gravifer commented on GitHub (Mar 23, 2024): seems like a mishandled corner case? @zadjii-msft > Took quite a long time to figure out I had to drag a tab in-between two other tabs to get it to move to a different window and not at the end of other tabs.

claunia commented

@agyild commented on GitHub (Aug 22, 2024):

seems like a mishandled corner case? @zadjii-msft

Took quite a long time to figure out I had to drag a tab in-between two other tabs to get it to move to a different window and not at the end of other tabs.

I only found out about this after a Google search which is non-intuitive UX design. Ideally, moving tabs between windows should replicate the behavior in web browsers. @zadjii-msft

@agyild commented on GitHub (Aug 22, 2024): > seems like a mishandled corner case? @zadjii-msft > > > Took quite a long time to figure out I had to drag a tab in-between two other tabs to get it to move to a different window and not at the end of other tabs. I only found out about this after a Google search which is non-intuitive UX design. Ideally, moving tabs between windows should replicate the behavior in web browsers. @zadjii-msft

claunia commented

@fireattack commented on GitHub (Aug 22, 2024):

Also when you are tearing a tab, the cursor icon is always "🚫" which seems to imply it's an invalid operation, but in reality, you can tear it off.

@fireattack commented on GitHub (Aug 22, 2024): Also when you are tearing a tab, the cursor icon is always "🚫" which seems to imply it's an invalid operation, but in reality, you can tear it off.

claunia commented