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

91–100 of 177 posts

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

#91

Post by erik_seaberg »

Someone wrote: post #50
thrdbndndn wrote: post #18

A kinda relevant question. I use Windows most of time. Like the author, I have bunch of CLI scripts (in Python mainly) which I put into my ~/bin/ equivalent. After setting python.exe as the default program for `.py` extension, and adding `.py` to `%pathext%`, I can now run my ~/bin/hello.py script at any path by just type `hello`, which I use hundreds of time a day. I now use Linux more and more (still a newbie) but…

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

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

#92

Post by tgv »

mixmastamyk wrote: post #88
c22 wrote: post #73

I guess this works great right up to when the contents of ~/bin/ are added to a CSV for whatever reason.

Use TSV instead.

So much better. And you don't have the ridiculous "localization" of csv: over here, the field separator defaults to a semicolon. I suppose someone thought it was so terribly important to have a decimal comma in a csv file that any form of common sense went out of the window.

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

#94

Post by card_zero »

meken wrote: post #62
thrdbndndn wrote: post #18

A kinda relevant question. I use Windows most of time. Like the author, I have bunch of CLI scripts (in Python mainly) which I put into my ~/bin/ equivalent. After setting python.exe as the default program for `.py` extension, and adding `.py` to `%pathext%`, I can now run my ~/bin/hello.py script at any path by just type `hello`, which I use hundreds of time a day. I now use Linux more and more (still a newbie) but…

Your example got me thinking about the difference between how the windows shell and Unix shell is designed. Seems like the windows shell knows about extensions, whereas the Unix shell does not That’s an interesting feature for a shell to have. Thanks!

[flagged]

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

#95

Post by malux85 »

bqmjjx0kac wrote: post #12

> Because my shell script names tended to be short and pithy collections of lowercase characters, just like the default system commands, there was no telling when Linux would add a new command that would happen to have the same name as one of mine. Not sure I understand this problem. I just put my bin directory at the front of $PATH rather than the end. To browse my commands, I simply `ls ~/bin`.

ls ~/bin is wayyyyy slower to type than ,

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

#96

Post by tanelpoder »

Great idea! And if for some reason you feel like your filenames should stay as they are (without a comma), you could just add symlinks to all executable files in your bin directory:

  $ cd ~/bin
  $ for x in $(find . -type f -perm /a=x -exec basename {} \;) ; do echo $x ; done
  temps

  $ for x in $(find . -type f -perm /a=x -exec basename {} \;) ; do ln -s $x ,$x ; done

  $ ls -l
  total 4
  lrwxrwxrwx 1 tanel tanel   5 Jun 23 16:38 ,temps -> temps
  -rwxr--r-- 1 tanel tanel 251 May 30 23:26 temps

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

#97

Post by setopt »

codetrotter wrote: post #3

I 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…

I tend to make all my git aliases into two-letter combos starting with g. So `gs` is `git status`, for example. Once in a while I actually really need GhostScript though, it’s brilliant for e.g. embedding fonts into PDF files. Usually I then go with `env gs`.

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

#99

Post by dotancohen »

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 sure would have helped to job some memories about why each script was written, before opening it.

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

#100

Post by heisenbit »

LeoPanthera wrote: post #22
thrdbndndn wrote: post #18

A kinda relevant question. I use Windows most of time. Like the author, I have bunch of CLI scripts (in Python mainly) which I put into my ~/bin/ equivalent. After setting python.exe as the default program for `.py` extension, and adding `.py` to `%pathext%`, I can now run my ~/bin/hello.py script at any path by just type `hello`, which I use hundreds of time a day. I now use Linux more and more (still a newbie) but…

Simply remove the .py from the filename. It's perfectly acceptable to call it "hello". I can't think of a downside to the shebang. If you really wanted to run the script with a different interpreter, just specify it. "nohtyp hello" or whatever. If that still bothers you too much, you could define an alias in your shell startup. For example, in bash, you might do: alias hello="python3 /path/to/hello.py" If you were so…

Node seems to be partial to whether one has a .mjs or not on the filename.
Post reply on HN