You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thanks for your life-changing script. I especially admire anyone who tries to stay posix compliant and not bash out.
Unfortunately, I don't understand why the configuration snippets in the README test for the existence of the history file. After all, theme -l gives a valid output whether the file exists or not. The snippets didn't work for me at first because I set XDG_CONFIG_HOME and the awk statements in theme.sh determine the location of the history file with the environment variables:
If there is no error in my logic, here is already a PR for the change.
The text was updated successfully, but these errors were encountered:
jrd-oje
changed the title
Why test for history file in configurations snippets?
Why test for history file in configuration snippets?
Nov 19, 2023
jrd-oje
changed the title
Why test for history file in configuration snippets?
Why test for history file in configuration snippets in README?
Nov 19, 2023
Hi, thanks for your life-changing script. I especially admire anyone who tries to stay posix compliant and not bash out.
Unfortunately, I don't understand why the configuration snippets in the README test for the existence of the history file. After all, theme -l gives a valid output whether the file exists or not. The snippets didn't work for me at first because I set XDG_CONFIG_HOME and the awk statements in theme.sh determine the location of the history file with the environment variables:
If there is no error in my logic, here is already a PR for the change.
The text was updated successfully, but these errors were encountered: