Skip to content

fixup to async_prompt_enable flag - #89

Open
ilyagr wants to merge 2 commits into
acomagu:masterfrom
ilyagr:fixup-disabling-async
Open

fixup to async_prompt_enable flag#89
ilyagr wants to merge 2 commits into
acomagu:masterfrom
ilyagr:fixup-disabling-async

Conversation

@ilyagr

@ilyagr ilyagr commented Jun 7, 2025

Copy link
Copy Markdown
Contributor

316aa03 did not disable fish-async-prompt sufficiently for me when I used

if test "$TERM_PROGRAM" = vscode
    set -g async_prompt_enable 0
end

fish-async-prompt still interfered with the VS Code Terminal.

This PR together with the above snippet seemed sufficient to disable fish-async-prompt to a degree that worked around the VS Code problem (see microsoft/vscode#250916 for more details about the VS Code problem).


Warning: Note that, like before, this will only work correctly if async_prompt_enable is set to 0 before the first prompt is drawn.

I'd love to remove this limitation, but that would require understanding how to recover the old fish_prompt. Update: Something like this might actually be enabled by #86, but that PR is complicated enough that I don't want to rely on it without thinking about it quite a bit more.

@ilyagr
ilyagr force-pushed the fixup-disabling-async branch 6 times, most recently from e3a4dda to 67d259c Compare June 7, 2025 05:37
ilyagr added 2 commits June 7, 2025 17:37
316aa03 did not disable fish-async-prompt sufficiently for me
when I used

```fish
if test "$TERM_PROGRAM" = vscode
    set -g async_prompt_enable 0
end
```

fish-async-prompt still interfered with the VS Code Terminal,
but adding this seemed to fix it.
@ilyagr
ilyagr force-pushed the fixup-disabling-async branch from 67d259c to 79cb9c4 Compare June 8, 2025 00:37
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.

1 participant