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

101–110 of 177 posts

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

#101

Post by o11c »

dotancohen wrote: post #99

I was recently poking around ~/.local/bin/ when I noticed that it had dozens of executables that I don't remember putting there. Mostly pyside things, but some other scripts as well. I really had to open each to jog my memory, especially about which scripts I had written myself and which were by other people. The idea about starting my own scripts' names with a comma would have made the job go much faster, and I'm su…

Normally ~/.local/bin/ is only for installed scripts; locally-written ones go in ~/bin/

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

#103

Post by L8D »

mozman wrote: post #4

When 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?

I think the hip thing to do is just use your spare time to build stuff, and organically learn from building stuff. Self-sufficiency, creativity and generally being a self-starter is what's hip. More time spent building translates into an incentive to pickup tricks and relying on yourself to find hip solutions to actual problems.

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

#104

Post by olejorgenb »

morningsam wrote: post #80

An alternative method for avoiding collisions in PATH is to use really long executable names that are unlikely to be used by other executables and then have shorter aliases for them in your bashrc. The aliases won't affect executables called from within scripts and you can still refer to your executables by their long names in your own scripts. One drawback is that this doesn't have the same tab completion ergonomics…

> One drawback is that this doesn't have the same tab completion ergonomics, which I have to admit is really nifty.

They do in zsh

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

#105

Post by zogrodea »

zuminator wrote: post #102
TrianguloY wrote: post #77

Those can really be called comma_nds! Ahem. Nice idea though, I think I'll start using it...

Surely ,nds?

I think "comma_nds" ("commands" if you remove the underscore) makes the pun mkre obvious.

I didn't get it at first thought, thinking of the .nds file extension for Nintendo DS ROMs.

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

#106

Post by skeledrew »

erik_seaberg wrote: post #91
Someone wrote: post #50

Earlier quoted context omitted.

> but then you have to add a shebang line directly to the script itself, which I always feel uncomfortable since it's hard-coded It won’t directly help reach your goal, but it is semi hard-coded. The ‘correct’ (but see https://unix.stackexchange.com/a/29620 for some caveats) way to write a shebang line is #!/usr/bin/env python That will make it run the first python in your path. > what if in future I don't want to ex…

To be excruciatingly correct, we should specify python2 or python3, because they can't interop and probably never will.

I think at this point we can rest easy that python2 has finally been fully purged from default installs. Heck a few weeks ago I installed Kubuntu 24.04 base and there was no Python at all...

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

#107

Post by erik_seaberg »

skeledrew wrote: post #106
erik_seaberg wrote: post #91

Earlier quoted context omitted.

To be excruciatingly correct, we should specify python2 or python3, because they can't interop and probably never will.

I think at this point we can rest easy that python2 has finally been fully purged from default installs. Heck a few weeks ago I installed Kubuntu 24.04 base and there was no Python at all...

Debian stable doesn't have "python" anywhere on my PATH, for a good reason IMHO. Shebangs say "/usr/bin/env python3" or hardcode "/usr/bin/python3".

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

#109

Post by d0gsg0w00f »

mozman wrote: post #4

When 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?

Also in "management", also feel like my skills will atrophy if I don't keep up.

What I do is make tools to make my life easier. For example, if there's a web service at work I use for mundane lookups I'll find out if it has an API and write a CLI for it to speed up my daily grind. Once it's tuned to my liking I'll share it with the team. I do struggle to convince others to try it. Not sure why. But I don't really care because I use the tools every day.

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

#110

Post by vincent-manis »

D-Coder wrote: post #90
MadnessASAP wrote: post #84

Earlier quoted context omitted.

It's can be traced back to the roots of each OS. Windows has it's heritage in the land of DOS where files had an 8 character name with a 3 character extension and that extension carried meaning for the OS. Linux being of Unix ancestry which had no such concept as a file extension. It was the responsibility of the application or kernel to discern what type a file was. Typically by the first few bytes of a file and han…

Speaking of heritage... 8+3 goes back at least to DECSystem-10 on PDP-10s.

6+3 on DEC TOPS-10.
Post reply on HN