-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
[starship] eval after bleopt necessary? #333
Comments
Sorry for the long blank, but the provided context is unclear. At least, I cannot reproduce the problem with the settings you provided. The general answer to a question on the ordering of the configuration is mentioned in README §1.3. Whether To answer the question for your specific case, I need clarifications and context from you. I'm sorry, but I need to ask many quetions.
|
ble version:
0.4.0-devel4+f16c0d8
Bash version:
5.2.15(1)-release (x86_64-pc-linux-gnu)
In
/etc/bashrc
I have:When using the newest version of
ble.sh
(latest commit from master branch), I need to run theeval
command a second time in~/.bashrc
after the section with allbleopt
andble-bind
statements, just before[[ ${BLE_VERSION-} ]] && ble-attach
~/.bashrc
I am unsure if this is a packaging issue, as this happens on NixOS 23.05, with a custom packaged version of
ble.sh
. When using the provided0.4.0-devel3
release archive from GitHub, the change is not required for starship to start with a singleeval
in/etc/bashrc
.Without the second
eval
,ble.sh
0.4.0-devel4+f16c0d8
starts fine, but I only see thebash:$
prompt instead of the starship prompt.The text was updated successfully, but these errors were encountered: