Use $HOME/bin instead of ./bin in PATH export#387
Closed
xulfm wants to merge 1 commit into
Closed
Conversation
Member
|
This is doing something different. ./bin looks for the bin in the current directory. Usually used for app development. You're looking to add your ~/bin to path. That's fine too, if you need it, but you can just add that in your ~/.bashrc file 👌 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use
$HOME/bininstead of./binin default PATH setupThis update changes the
PATHexport indefault/bash/shellfrom:export PATH="./bin:$HOME/.local/bin:$HOME/.local/share/omarchy/bin:$PATH"
to:
export PATH="$HOME/bin:$HOME/.local/bin:$HOME/.local/share/omarchy/bin:$PATH"
Why this matters:
I needed this change to install the Mullvad Browser
Using
./binmakes PATH resolution depend on the current working directory, which can lead to unpredictable behaviour or security concerns.Replacing it with
$HOME/binaligns with standard Unix/Linux environment setups and ensures PATH is consistently scoped to the user’s environment, not the current directory.This small change improves safety and reliability, especially in multi-shell or scripting environments.