I’m crossposting this here
A) So I can see if I know how to cross post lol
B) To bring attention to the [email protected] community here, as it it woefully small and could use some publicity, especially to those who can help more than the noobs seeking it out
C) Hopefully get the answer I seek.
…did the crosspost work? (Ayy alright!)
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!
related practice (and maybe less odd) - I prepend some function names to “group” them.
Before using topgrade I wrote some functions to automatically update package managers e.g. apt, cargo, flatpak. so I created
uu_apt,uu_cargo, etc. Prepending plays well with the Tab autocomplete in the shell.This is basically what I’ve done so far, actually. I just want to polish it up just a hair enough that I can send it to friends or transfer it between distros, the name is terrible but descriptive (and long, but tab-complete so I said fuck it for the time being). Just need to rename it and change a few lines to “$USER” to make it a bit more polished.
For instance one I really need to rename is just a batch converter using ffmpeg, atm I just called it batchffmpeg but that is too long, might just call it bffmpeg and keep it rolling, short enough and likely not taken. The others I’m more worried about conflicts but I suppose as someone else pointed out the tried and true “band name” method (think of one and just search “google” to see if taken) should handle it. Never thought about that lol, one of those solutions that’s just too simple I missed it while looking higher.