Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Start all of your commands with a comma (2009)

rhodesmill.org

Post reply on HN
Print view View original

31–40 of 252 posts

Re: Start all of your commands with a comma (2009)

#33

Post by Levitating »

laughing_snyder wrote: post #29

> Like many Unix users, I long ago created a ~/bin/ directory in my home directory `.local/bin` seems to be much more common in my experience for this use case. And for good reason.

~/bin is actually created per default on OpenSUSE (though it's removal has been discussed several times).

Re: Start all of your commands with a comma (2009)

#34

Post by dark-star »

impoppy wrote: post #27

Why so many people use ~/bin/? What’s wrong with ~/.local/bin?

~/bin/ preceeds the XDG Base Directory Specification.

~/.local was only invented around 2003 and gained widespread usage maybe 15 years or so ago...

People used ~/bin already in the 90s ;-)

Re: Start all of your commands with a comma (2009)

#35

Post by 112233 »

mathfailure wrote: post #9

I didn't like the idea. I prefer the alternative approach: _I_ decide the order of dirs in the PATH env. If I introduce an executable with a name, that overrides a system one - I probably do that intentionally. If I introduce an alias (like `grep='grep --binary-files=without-match --ignore-case --color=auto`) that matches the name of a system binary - I probably do that intentionally. And if I EVER need to call grep…

Any severe side effects so far? Have you set PATH up somehow so it is effect only on interactive prompt, and not in the launched processes?

Because I cannot imagine much 3rd party scripts working with random flags added to core tools

Re: Start all of your commands with a comma (2009)

#36

Post by albert_e »

zdc1 wrote: post #18
dadandang wrote: post #3

,Start all of your commands with a comma

Should be titled Prefix your script names with a comma . Current title is a little clickbait-y through its ambiguity.

Agree.

I thought the title meant I should type ,ls instead of ls.

Re: Start all of your commands with a comma (2009)

#37

Post by mid-kid »

mathfailure wrote: post #9

I didn't like the idea. I prefer the alternative approach: _I_ decide the order of dirs in the PATH env. If I introduce an executable with a name, that overrides a system one - I probably do that intentionally. If I introduce an alias (like `grep='grep --binary-files=without-match --ignore-case --color=auto`) that matches the name of a system binary - I probably do that intentionally. And if I EVER need to call grep…

Either adding your script directory in front of the PATH, or creating `alias` that provide a full path to your script where a conflict exists, makes a whole lot more sense to me.

I've never had this collision problem yet, despite appending my script directory to the end, but I'll use either of the above solutions if that ever becomes a problem.

Re: Start all of your commands with a comma (2009)

#38

Post by [deleted] »

fragmede wrote: post #28
mathfailure wrote: post #9

I didn't like the idea. I prefer the alternative approach: _I_ decide the order of dirs in the PATH env. If I introduce an executable with a name, that overrides a system one - I probably do that intentionally. If I introduce an alias (like `grep='grep --binary-files=without-match --ignore-case --color=auto`) that matches the name of a system binary - I probably do that intentionally. And if I EVER need to call grep…

curious if you're customizing anyway, why not use eg ripgrep?

[deleted]

Re: Start all of your commands with a comma (2009)

#39

Post by yunohn »

I read this blog a few years ago, and implemented it soon after with a refresh of my rc files and shortcuts. Gamechanger - has helped me every single day since. It’s easy to remember, autocompletes easily, and adds a little flair of personalization.
Post reply on HN