"Open in Terminal" to start in existing terminal instances by default?

[vadimkantorov]

Right now, it always spawns a new Terminal instance / window which can be a tad slower than just spawning a new tab in existing instance. This can be compared as opening an HTML file from disk which usually would open it in existing Chrome instances and just open a new tab.

Propose to have a discussion to have the same behavior for Terminal by default (great that an option already exists in the config though! thanks to @237dmitry for pointing it out!)

[237dmitry]

This option already exists

"windowingBehavior": "useAnyExisting"

[vadimkantorov]

thank you! great to know! i'll then repurpose this issue to propose to make it default

[zadjii-msft]

Thanks for the suggestion! Until we've got tab tear-out sorted out, I've been reluctant to change any defaults to useExisting. That would just make the windows glom together and now you'd be stuck without it being able to tear into it's own window. Trust when I say, when tear-out is ready for stable releases, we'll be changing the default to useExisting.

There's also /dup #7071 for adding a separate setting to control the shell context menu's behavior separate from the globals, but that's quite a bit farther out.

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

[vadimkantorov]

One nuance, in Chrome it would use last active window for opening disk files, not just "any existing window"

[zadjii-msft]

One nuance, in Chrome it would use last active window for opening disk files, not just "any existing window"

That's literally exactly what useExisting does