Start all of your commands with a comma (2009)
rhodesmill.org
Start all of your commands with a comma (2009)
1–10 of 177 posts
Re: Start all of your commands with a comma (2009)
#2This works for text-expansion snippets too. All of the text expansions that I do with Alfred (other tools might work, too) are all comma phrases. I realize that writing English or even programming scripts/tag, I'd never (not so far) encounter a word or text that starts with a comma immediately followed by anything. I used to use period but have stumbled on instances such as file extension where a period can be followed by words.
Re: Start all of your commands with a comma (2009)
#3I use short custom command names like aa, st, di, dp, cm and le in some thin wrappers around git.
One of these names actually collides with a utility that is installed by default on some systems.
Doesn’t matter to me. I have my own bin dirs before the system dirs in my path, so mine “win”, and I’m not really interested at all in the tool that mine has a name collision with.
If someone were to make a useful to me tool that collided with one of my own tools, I’d probably sooner alias that other tool to a new name that didn’t collide with mine, than to change any of my own tool names.
It’s just too comfortable to use these two-character tools of mine.
Re: Start all of your commands with a comma (2009)
#4When I read the headline I thought this was going to be a terrible idea but I quite like it, especially the bit about using tab to list all your tooling.
Anecdotally I haven’t had many namespaces collisions recently. I’ve also let myself go a bit after going into management. My tech skills are 10 years too old.
Any tips from someone else on where they started to be hip again?
Re: Start all of your commands with a comma (2009)
#5I use short custom command names like aa, st, di, dp, cm and le in some thin wrappers around git. One of these names actually collides with a utility that is installed by default on some systems. Doesn’t matter to me. I have my own bin dirs before the system dirs in my path, so mine “win”, and I’m not really interested at all in the tool that mine has a name collision with. If someone were to make a useful to me tool…
This. 1-3 character names should be reserved for user aliases/functions/scripts and standard utilities.
Re: Start all of your commands with a comma (2009)
#6Good idea overall, I must say.
It's one more key press, but I'm pretty sure I would use underscore for the first character.
Re: Start all of your commands with a comma (2009)
#7I use short custom command names like aa, st, di, dp, cm and le in some thin wrappers around git. One of these names actually collides with a utility that is installed by default on some systems. Doesn’t matter to me. I have my own bin dirs before the system dirs in my path, so mine “win”, and I’m not really interested at all in the tool that mine has a name collision with. If someone were to make a useful to me tool…
All my personal commands begin with 'j'. Got real fun when java came around. Using commas is a rather interesting idea.
But at least I did not start them with a 'k' (KDE) :)
Re: Start all of your commands with a comma (2009)
#8This works for text-expansion snippets too. All of the text expansions that I do with Alfred (other tools might work, too) are all comma phrases. I realize that writing English or even programming scripts/tag, I'd never (not so far) encounter a word or text that starts with a comma immediately followed by anything. I used to use period but have stumbled on instances such as file extension where a period can be follow…
> I'd never (not so far) encounter a word or text that starts with a comma immediately followed by anything.
Agreed. I prefer using `!bang`s for the same reason for expanding text.
Re: Start all of your commands with a comma (2009)
#9Never thought about that, cool!
Re: Start all of your commands with a comma (2009)
#10best idea i've read in a while, will do