-
Notifications
You must be signed in to change notification settings - Fork 424
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
Does not work with 'set -o nounset' because of undefined variables usage #354
Comments
For reference (at least for myself), here is the relevant part of the
About your question, I think it would be a big effort (if even possible) to make liquidprompt clean for I don't intend to spend my own time resources on this effort, but patches are welcome! Note that on Ubuntu, filename completion seems to have issues working with |
Anyway, I have some work in progress for liquidprompt in the |
set -o nounset I've only fixed usage of variable that were used at runtime in my environment. 'ret' remains unfixed.
I've fixed all cases I found so far with a8114dd. |
set -o nounset I've only fixed usage of variable that were used at runtime in my environment. 'ret' remains unfixed.
I have both manually inspected the source for However, as dolmen noted in #354 (comment), |
Liquidprompt does not work when enabling the BASH 'nounset' feature, each prompt shows the three following warnings:
Would it be possible to make sure variables are defined before using them?
The text was updated successfully, but these errors were encountered: