Just name your script with your credit card numbers, so you’re pretty sure you won’t have any collisions… Don’t hesitate to let me know when you’ve done it :)

Hahaha when I click the link from /all it takes me to

https://zerobytes.monster/c/beautifulfemales

When I go to the comments first then click the link it goes to

https://lemmy.dbzer0.com/post/1464137

If you use them for your use only, or want them “cleanly” organized, consider prefixing it with something personal to you (or a generic one such as my_). For example, I’d prefix them with l_: my_rename_photos.sh, my_lightson.sh, etc.

If there’s a lot of them, write a wrapper script which would call the individual scripts from a common location (/usr/share/my-scripts/). Then, you can only make sure your wrapper script is aliased/moved in the PATH. Example: my rename, my lightson, etc.

which commandname will tell you if there’s a command already by that name on your system without having to run anything.

This only finds things in places stored in the $PATH environment variable, though.

You could query your package manager to see what packages for your distribution might contain the command name, but 1) that will also turn up support files and the like and 2) Not all distros have the same commands, especially once you get beyond the core Unix/Linux command set.

e.g. on a system with apt, I can run apt contains commandname and get a list of everything containing “commandname”

Another user suggested prefixing with my_, but you might consider using your initials, a short form of your username or some other identifier instead. e.g. Everyone is “me/my” to themselves, but fewer people share your initials.

Also, a suffix might actually be a marginally better choice depending on your tab-completion preferences.

There’s precedent for some actual “official” commands using a .suffix style, especially when multiple packages have their own version of a particular command, or a minor variant. On my computer I have things such as uncompress.real, vim.tiny, lzip.plzip and telnet.netkit, for example.

Something like scriptname.arcslime would fit right in, whether or not scriptname is a thing in its own right or not.

frankly if I already had the names, I would just search for " cli" or " bash" and see what comes up.

If you’re using a Debian based distro, you can search through contents of packages to see if there’s a conflict:

E.g. apt-file search /usr/bin/sh

Don’t know the site you’re looking for - might have never seen it. But I saw a tip a while back: name YOUR scripts something like “,script” (with a comma, or other confortable to type character as 1st character). It would be odd to ever find a colision.

I just don’t do that though! Too odd!

My script names are basically

downloadallmystuffbackplease.sh

bbutimnotonmyrpi4.sh

aptthewholething.sh

jesusimfuckingdum.sh