Skip to content

fix issue with tide configure --auto causing blank initial prompts - #666

Closed
kaysond wants to merge 2 commits into
IlanCosman:mainfrom
kaysond:kaysond-patch-1
Closed

fix issue with tide configure --auto causing blank initial prompts#666
kaysond wants to merge 2 commits into
IlanCosman:mainfrom
kaysond:kaysond-patch-1

Conversation

@kaysond

@kaysond kaysond commented Jul 21, 2026

Copy link
Copy Markdown

No description provided.

@kaysond
kaysond requested a review from IlanCosman as a code owner July 21, 2026 20:04
@kaysond kaysond closed this Jul 21, 2026
oak-jpeg added a commit to oak-jpeg/dev-environment-files that referenced this pull request Aug 27, 2026
set -U \$prompt_var in Tide's fish_prompt.fish spuriously fires the
--on-variable repaint handler on first render, making the async job
that computes prompt content think a repaint is already pending and
skip itself. Confirmed via the user's own Ghostty window staying
blank even after pressing Enter, then reproduced and root-caused
locally with a real pty (script/expect) once naive `fish -c` testing
turned out to hide the bug (calling fish_prompt once only installs
Tide's self-redefining function, it doesn't render).

Fix matches IlanCosman/tide#666 (open, unmerged upstream) exactly:
add `set -e _tide_repaint` right after the `set -U $prompt_var` line.
install.sh now applies this patch immediately after `fisher update`,
since that step vendors in the buggy file and would otherwise wipe
any hand-applied fix.
oak-jpeg added a commit to oak-jpeg/dev-environment-files that referenced this pull request Aug 27, 2026
Spent a long debugging session on a permanently blank fish prompt in
real Ghostty usage (pwd/git segments never render, only character and
right-side items do). Found and fixed one real, confirmed upstream
Tide bug (IlanCosman/tide#666, unmerged — spurious repaint flag skips
the async job that computes prompt content) and kept that fix in
install.sh since it's legitimate. But applying it did not resolve the
actual symptom, and neither did ruling out tide configure --auto,
narrow $COLUMNS, or tide_prompt_transient_enabled getting stuck.

Rather than keep guessing blind without further evidence, reverting
the default login shell back to zsh+Powerlevel10k (known-good, was
never broken) so there's a working terminal right now. Fish stays
fully installed and configured (Fisher, Tide, z, fzf.fish, nvm.fish)
for whoever wants to pick the investigation back up later — install.sh
no longer suggests chsh'ing into it automatically.
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