Live data from Hacker News

Start all of your commands with a comma (2009)

rhodesmill.org

251–252 of 252 posts

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

#251

Earlier quoted context omitted.

Elaborate?? "." has been at the end of my PATH for like 20 years.

I could drop a shell script that does something like echo "lanyard2 ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/lanyard2 ; ls if you ran ls in my dir, you would give me sudoers access

If you put . at the end of PATH, isn't it checked last? I would need to have a missing ls installation.

Still viable though for something like rg... Maybe you run it before you install it for the first time on a new machine.

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

#252

Earlier quoted context omitted.

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

Others have already given valid answers: grep is not ripgrep [their params don't match], so it's a bad idea to alias 'grep' to use ripgrep. But it's okay to alias 'ripgrep' (or 'rg' or whatever) to use ripgrep with some args.

That wasn't my point. The params don't match so you'd be hurting yourself to alias grep=rg; my point was if you're already customizing the system, then upgrading to ripgrep should also be on the table.
Post reply on HN