Collecting linux shell scripts/commands
from Localhorst86@feddit.org to linux@lemmy.ml on 15 Jan 15:13
https://feddit.org/post/6856663
from Localhorst86@feddit.org to linux@lemmy.ml on 15 Jan 15:13
https://feddit.org/post/6856663
We all know this. We need to do a specific task and with the help of the internet we find a specific tool alongside command line parameters to do the job right from the shell.
What is a good way of collecting/documenting these snippets on your own for future reference and use? Just a text file in the home folder?
threaded - newest
There is a command called
tldr. it’s works similar to what you have described.I’d try a wiki of some sorts. Personally we collect a lot of stuff in our bookstack instance. Recently we’re looking into tools that can save a page for offline usage.
If you like TUI you might find this useful:
github.com/knqyf263/pet
Thanks, this looks like the tool I was looking for. Being able to store the snippets alongside a description sounds perfect
I use a text file and have an alias to access it quickly.
I do mine in Obsidian, I just have a folder for ‘computer notes’ and whenever I figure out a new thing I drop it in there.
Some stuff I use often I set up as an alias too. So for example I have
alias yt=‘yt-dlp -f “bestvideo[ext=mp4]+bestaudio[ext=m4a]/mp4”’for my most commonly used yt-dlp settings, so now I can just doyt [URL of video]to quickly download something from YouTube. Oralias rs=“sudo rsync --ignore-existing -rav”for my rsync settings for a specific backup folder I copy a lot.I prefer my
-f “bestvideo[ext=mp4]+bestaudio[ext=m4a]/best[ext=mp4]/best” --concurrent-fragments 12 --throttled-rate 100K -o “%(uploader)s/%(playlist_title|)s/%(playlist_index&{} - |)s%(title)s.%(ext)s”Since it saves it based on the channel and if is a playlist, it makes a folder based in that
-Not sure if
–concurrent-fragments 12 --throttled-rate 100Kdoes actually something.I’m interested in the rsync part for backups, do you have a good guide or video for that? Thanks
I don’t really have a guide or anything for it to hand, but essentially what that alias is doing is:
rsync= running rsync–ignore-existing= as you might have guessed, this tells rsync not to copy a file if it already exists at the destination.-rav= additional arguments. r = recursive, IE also copy subfolders. a = archive mode, preserves things like symlinks etc. and v = verbose, just tells you extra info about what’s going on.So with that alias, I can just type
rs [target folder] [destination folder]and it’ll copy it across exactly as it is, ignore anything that’s already there and tell me precisely what it’s doing.What if I added my own local server in dolphin? Can I use it’s path to sync a local (Linux) folder to the server?
Hmm, I have no idea to be honest! I just back up to an external drive. It does look like you can rsync to anything you have SSH access to, but I’ve never tried it personally.
In my obsidian i use the daily note feature heavily and if i come across a useful snippet or info i will add a tag and content like below. I found tagging to be helpful because i do not have to spend effort up front putting the file in the “right” folder. I have cleaned some of these up by removing them from my daily notes and into dedicated notes, but only after i have collected quite a few for a specific language or tech and there is a need for me to put more structure around the information.
#codesnippet/<language or tech stack> Write a description to help me remember what this is for
<insert code here>
I take notes in Joplin with the command and a breakdown of any flags, parameters, etc, and what they everything means/does.
If you’re into self hosting, Bytestash is very nice!
I just use Zsh’s command history, coupled with a bunch of functions and aliases to set up different HISTFILE values for different workflows.
I keep HISTFILEs clean by prepending a whitespace before commands that I don’t want to remember, which unfortunately gave me the habit of doing that on Bash when Zsh isn’t available (which is ineffective at best, and actively annoying at worst).
.
Just learn the basic POSIX commands (there’s probably 20-25) and understand pipes. Then you can do pretty much anything you’re likely to need from the command line. Sure, there will be more modern flashy friendly tools that come along. Some you’ll integrate into what you do. Some won’t have enough staying power to remember.
No notes. No googling or LLM. Just don’t skip to the end.
Ctrl+R
spend more time in the shell. you will naturally learn the most commonly used commands and useful flags for them. soon you will be surprised by how much you know. having good typing speed helps reduce the friction a lot. i have not found need to specifically “memorize” anything consciously.
for obscure things, write a script and put it in a scripts folder, have a comment at the top explaining what it does for reference later.
just alias them.
commands.txt every command with a one line description and a separator.
I have a folder in my nextcloud, where I save scripts I find and/or use regularly.
I just keep my history file around and have set it up to never truncate. Then
grepor^R.i usually get to where i’m going using man pages rather than copying wholesale from the web, but when i find something worth saving i usually put the snippet in its own script in
~/.local/bin, which is in myPATH. with some modifications to make it generic, of course.i use a joplin notebook. its like a private wiki, and it works on android too.
I push them up to my self hosted gitlab server.