Terminal: [Setting] New tab button should open another of the currently selected tab

[matthew4850]

• Your Windows build number: 10.0.18890.1000

• What you're doing and what's happening: When you press the add tab button it always opens cmd.

• What's wrong / what should be happening instead: It should open another of the currently viewed tab.

[zadjii-msft]

It actually opens a new tab of whatever the defaultProfile is, which is the cmd profile by default currently.

We can add a setting that new tab opens a new instance of the active tab instead.

[HBelusca]

I'm by the way wondering what happened to the Windows "Sets" feature that disappeared from the Insider builds some time ago...

[zadjii-msft]

this is a trap

I can't say anything about Sets, other than the fact that we wanted to ship a Terminal with tabs before they were able to get us top-level tabs. When Tabbed Sets makes a return, you better believe that we'll be working closely with them to make sure we have the tightest possible integration of our tabs and theirs.

[zadjii-msft]

I discussed this briefly with @DHowett-MSFT today. On the surface, this seems a bit like #1536, which was implemented in #1685. However, this actually has to do with specifically the behavior of the new tab _button_, not just the keybinding. I'm leaving this open to track _changing the behavior of the new tab button_.

[haolly]

As a end user, I understand "dumplicate current tab" means the new tab will be in the same directory as the source, but #1685 does not.
Seems like #1685 is just bind a shortcut to the plus + button's functionality