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

81–90 of 130 posts

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

#81

Post by SrslyJosh »

Maursault wrote: post #61

The comma is employed in bash and other shell for brace expansion.[1] I can't see how this would conflict with OP's master plan, but I have fundamental objections towards the depths of OP's laziness. Lazy is ok, but there should not be competition to see who can be laziest. At some point, things just won't compress any further, and the attempt at further streamlining efficiency beyond what is useful has a negative ef…

That's a lot of words to say "I don't like this" and insult folks who put time and effort into customizations that improve their own computing experience.

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

#83

Post by Maursault »

SrslyJosh wrote: post #81
Maursault wrote: post #61

The comma is employed in bash and other shell for brace expansion.[1] I can't see how this would conflict with OP's master plan, but I have fundamental objections towards the depths of OP's laziness. Lazy is ok, but there should not be competition to see who can be laziest. At some point, things just won't compress any further, and the attempt at further streamlining efficiency beyond what is useful has a negative ef…

That's a lot of words to say "I don't like this" and insult folks who put time and effort into customizations that improve their own computing experience.

> who put time and effort into customizations

I believe you have made my point quite well once it's understood you are here referring to none other than prefixing script names with a comma. Any words wasted on anything other than the subject is a waste of words, in your comment's case, both ad hominem and straw man fallacies.

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

#84

Post by nerdponx »

fragmede wrote: post #48
nerdponx wrote: post #22

Earlier quoted context omitted.

I wish it was easier to create "snapshots" of a particular set of environment variables in order to use them later as run environments. I also wish that Unix desktop environments generally made it easier to manage env vars, but that's another complaint. And don't get me started on PAM env vars...

https://direnv.net/

I use Direnv in all of my projects, but it doesn't make it any easier to manage consistent groups of env vars or assign different executables to run in different groups.

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

#85

Post by Jistern »

TacticalCoder wrote: post #33

I do something a bit special... Instead of naming my script foobarnator (and hence risking that another foobarnator may exist in the future and may clash with my script), I name my script foobarnatorToBeAliased.sh . Then in my list of aliases I alias foobarnator to foobarnatorToBeAliased.sh . The alias itself looks a bit weird in that to pass arguments to an aliased command you need to use a function (in Bash at leas…

I start my aliases with a period so that I have...

.foo1,.foo2, .foo3, and so on.

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

#87

Post by RajT88 »

lkxijlewlf wrote: post #50
prosaic-hacker wrote: post #12

I have used a similar windows trick. I wanted to add to the default window system a place for my library of tools. Most are "portable" cmd apps from various sources (sysinternals, nirsoft). I put them all into a directory called ] in the root of a drive. Because of some common layout of keyboards the \ and ] are near each other, or in reach of left and right pinkies I can type \]\ before the name of the tools. This m…

I put c:\tools in my path, then put shortcuts to all my tools in there (ie: shortcut to AgentRansack named ar). Now, I pull up the run command (WND+R) type ar and agent ransack opens.

Permissions!

Post-vista, c:\programdata\tools

Set yourself a %TOOLS% environment variable.

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

#88

Post by acomjean »

_blz2 wrote: post #13
reidjs wrote: post #2

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)

Is this comment from a bot? You just reiterated everything from the article.

You 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.

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

#89

Post by NateEag »

potiuper wrote: post #44
dang wrote: post #27

Earlier quoted context omitted.

Reposts are ok after a year or so. This is in the FAQ: https://news.ycombinator.com/newsfaq.html . Could you please review the site guidelines at https://news.ycombinator.com/newsguidelines.html and stick to them? Your last sentence there breaks more than one of the rules.

Again, to reiterate, the original comment was not a statement that this should not have been reposted. I am not sure how I could make that clearer? I have read the site guidelines. Many of them are subjective and inconsistent with unknown applicability. If you, as the administrator, are unable to accept that evaluation, then please just delete this account and all associated posts.

"Please don't comment about the voting on comments. It never does any good, and it makes boring reading."

That's what dang was referring to, I believe, not some hypothetical implication.

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

#90

Post by [deleted] »

Jistern wrote: post #85
TacticalCoder wrote: post #33

I do something a bit special... Instead of naming my script foobarnator (and hence risking that another foobarnator may exist in the future and may clash with my script), I name my script foobarnatorToBeAliased.sh . Then in my list of aliases I alias foobarnator to foobarnatorToBeAliased.sh . The alias itself looks a bit weird in that to pass arguments to an aliased command you need to use a function (in Bash at leas…

I start my aliases with a period so that I have... .foo1,.foo2, .foo3, and so on.

[deleted]
Post reply on HN