Skip to content
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

Hash disabled, but never re-enabled. #339

Open
Madalosso opened this issue Nov 11, 2024 · 0 comments · May be fixed by #340
Open

Hash disabled, but never re-enabled. #339

Madalosso opened this issue Nov 11, 2024 · 0 comments · May be fixed by #340

Comments

@Madalosso
Copy link

Madalosso commented Nov 11, 2024

By default,the ~/.bashrc file sources

~/.local/share/omakub/defaults/bash/rc

source ~/.local/share/omakub/defaults/bash/shell
...

Which disables hash at this line, and it never re-enables it.

It would be desirable to re-enable hash once the scripts are executed. Otherwise, it might conflict with other scripts trying to use it. (like, for instance, nvm loading script)

I'm unfamiliar with the usage of hash within these configuration files, nor do I have a clear idea where a hash -h should be placed to re-enable the command without undoing the intended goal with the disabled. Still, I assume it's a simple fix for whoever has context on its usage.

Madalosso added a commit to Madalosso/omakub that referenced this issue Nov 11, 2024
@Madalosso Madalosso linked a pull request Nov 11, 2024 that will close this issue
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 a pull request may close this issue.

1 participant