Fix Tide behavior under VSCode shell integration#645
Open
snoack wants to merge 1 commit intoIlanCosman:mainfrom
Open
Fix Tide behavior under VSCode shell integration#645snoack wants to merge 1 commit intoIlanCosman:mainfrom
snoack wants to merge 1 commit intoIlanCosman:mainfrom
Conversation
- preserve the real post-command status, pipestatus, and CMD_DURATION before VSCode prompt hooks mutate them. - avoid showing idle time as cmd_duration on empty prompts. - wrap the VSCode fish_prompt shim so Tide's trailing newline does not create an extra blank line before the cursor. - hide Tide's status item by default in VSCode shell integration, where VSCode already shows command status. - refresh VSCode's prompt markers after Ctrl+L to avoid sticky-command spacing glitches.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Motivation and Context
Closes #433
Screenshots (if appropriate)
How Has This Been Tested
Checklist