-
Notifications
You must be signed in to change notification settings - Fork 511
always runs in active terminal #1619
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
always runs in active terminal #1619
Conversation
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.
LGTM :)
cc @alexandair |
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.
LGTM
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.
LGTM! The package changes might have conflicts with the PR I merged earlier...
@TylerLeonhardt Thank you so much. It will make it much easier to use various shells. Azure Cloud Shell, I'm looking at you. :) It will work with multiple lines when a backtick is used as a continuation character, right? |
e79cf8a
to
453ebe8
Compare
I seem to have found a potential bug in VSCode with this change... can't merge this in until it's sorted: |
453ebe8
to
4c781fb
Compare
@TylerLeonhardt Excellent. |
PR Summary
fixes #1607
Note: I decided against having this behavior to be configurable. The thought was that most people will only use the PowerShell Integrated Console.
In #1607 I brought up worry about people getting confused that their intellisense cache was not updating if they use pwsh instead of PSIC... I think perhaps this is a worry that does not exist and if it does and they open an issue, we can educate them.
Thoughts?
NOTE this relies on an engine update to 1.29 which is the current release. We probably don't want to merge this in until 1.30 is released1.30 has been released
NOTE I seem to have found a potential bug (microsoft/vscode#64390) in VSCode with this change... can't merge this in until it's sortedThe bug has been fixed. We can probably merge this in when 1.31.0 drops.
PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an
x
between the square brackets.Please mark anything not applicable to this PR
NA
.WIP:
to the beginning of the title and remove the prefix when the PR is ready