Skip to content

shell: fix unable to resolve your shell environment with LAST_COMMAND #251431

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

Merged
merged 1 commit into from
Jun 13, 2025

Conversation

connor4312
Copy link
Member

Fixes #251328

@bpasero not sure if there was a particular reason to use regex vs this approach?

Fixes #251328

@bpasero not sure if there was a particular reason to use regex vs this approach?
@connor4312 connor4312 self-assigned this Jun 13, 2025
@connor4312 connor4312 enabled auto-merge (squash) June 13, 2025 19:00
@vs-code-engineering vs-code-engineering bot added this to the June 2025 milestone Jun 13, 2025
@bpasero
Copy link
Member

bpasero commented Jun 13, 2025

@connor4312 I actually never wrote any of that code, maybe @joaomoreno recalls. but I am happy to change it 🤞

@connor4312
Copy link
Member Author

connor4312 commented Jun 13, 2025

It looks like the regex was added alongside the markers in 1336b3d. I can't think of a case where switching to a "greedy search" until the last marker using lastIndexOf would regress anything.

@connor4312 connor4312 merged commit 1724128 into main Jun 13, 2025
8 checks passed
@connor4312 connor4312 deleted the connor4312/issue251328 branch June 13, 2025 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to resolve your shell environment: Unterminated string in JSON at position 1932 (line 1 column 1933)
3 participants