Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CmdLineArgs] "--keepOpen" to keep the window/tab/pane open after the process/profile has exited. #16497
base: main
Are you sure you want to change the base?
[CmdLineArgs] "--keepOpen" to keep the window/tab/pane open after the process/profile has exited. #16497
Changes from 8 commits
aece58f
8c2490e
ba5564b
fb530c5
9d6078a
2621322
6fe6d21
ee97500
21d0fc3
a25eef0
4241103
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it correct that this json code and the one in line 395 is used to read form/write to a WT arguments json file? Do I need to update a json schema? (I can't find one.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, that's pretty much it. The schema can be found at
terminal/doc/cascadia /profiles.schema.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this seems... weird. This should already be plumbed through to the
TermControl
somewhere else...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, right. It's not actually used by the
TermControl
. The pane itself handles that, in this blob of code:terminal/src/cascadia/TerminalApp/TerminalPaneContent.cpp
Lines 240 to 256 in 9c16c5c
Looks like that's specifically looking up the CloseOnExit value out of the profile, not the
TerminalSettings
. I bet you could update that to use the value from the TerminalSettings too.This code has an example in that file of getting settings from the cache:
terminal/src/cascadia/TerminalApp/TerminalPaneContent.cpp
Line 345 in 9c16c5c
That'll get you a
TerminalSettingsCreateResult
, who's.DefaultSettings()
will have the value you're looking for