Closed wrvsrx closed 7 months ago
tide configure --auto
is not intended to be used in config.fish
. It sets universal variables, so you just need to run it once and it will persist across shell instances.
I thought the tide configure --auto
command was meant for declaring configuration (#304). Since it is not used for declarative configuration, do we still need to wait for #304 to be resolved?
I thought the
tide configure --auto
command was meant for declaring configuration (#304). Since it is not used for declarative configuration, do we still need to wait for #304 to be resolved?
This just comes down to a semantics question over what 'declarative configuration' is. Perhaps I have the definition wrong 🤷♂️ . But the idea is that you run the command once, and there's no plan to change that.
Describe the bug
Using
tide configure --auto xxx
inconfig.fish
causes tide prompt not showing immediately in new shell. Prompt appears normally if I open fish by terminal (wezterm), this problem only occurs when open fish in another shell such asbash
orfish
.Steps to reproduce
~/.config/fish
bash --norc
, then executefish
inbash
.Screenshots
Environment
Output of
tide bug-report
:Additional context