3 ms·
This is a good trick to avoid collisions with system commands. Anytime you add one of your own executables to PATH, prefix it with a comma (,). This way you avo
by reidjs 4y ago
This is a good trick to avoid collisions with system commands. Anytime you add one of your own executables to PATH, prefix it with a comma (,). This way you avoid name collisions and have a handy way of seeing what commands are available on your system using tab completion (, then tab lists all of your personal executables)
- deleted 4y ago[deleted]
- _blz2 4y agoIs this comment from a bot? You just reiterated everything from the article.
- heleninboodler 4y agoThis is an explanation that the parent comment simply reiterated the point of the article rather than adding content.
- scubbo 4y agoThis is a link to a story titled "This is the title of this story, which is also found several times in the story itself": https://stuff.mit.edu/people/dpolicar/writing/prose/text/titleOfTheStory.html https://stuff.mit.edu/people/dpolicar/writing/prose/text/tit...
- acomjean 4y agoYou are right, but I’m guessing a lot of people don’t read the linked article. It’s a pretty good summation. Though it doesn’t mention using ~/bin. I use that but don’t add it to my path, so I have to explicitly call my scripts. The comment history suggests it isn’t a bit though.
- behnamoh 4y agoRelated to GP, here's an interesting article: https://rhodesmill.org/brandon/2009/commands-with-comma/ https://rhodesmill.org/brandon/2009/commands-with-comma/