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?

  • whoareu
    link
    fedilink
    161 month ago

    There is a command called tldr. it’s works similar to what you have described.

  • Random Dent
    link
    fedilink
    English
    8
    edit-2
    1 month ago

    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 do yt [URL of video] to quickly download something from YouTube. Or alias rs="sudo rsync --ignore-existing -rav" for my rsync settings for a specific backup folder I copy a lot.

    • Dragonish
      link
      fedilink
      21 month ago

      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/ Write a description to help me remember what this is for

    • @Cris16228@lemmy.today
      link
      fedilink
      1
      edit-2
      1 month ago

      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

      • Channel
        • Playlist (if is a playlist, otherwise save inside channel)
            • title.extension (if not a playlist, it doesn’t add the -

      Not sure if --concurrent-fragments 12 --throttled-rate 100K does actually something.

      I’m interested in the rsync part for backups, do you have a good guide or video for that? Thanks

      • Random Dent
        link
        fedilink
        English
        2
        edit-2
        1 month ago

        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.

  • Johannes Jacobs
    link
    fedilink
    21 month ago

    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.

  • @harsh3466@lemmy.ml
    cake
    link
    fedilink
    21 month ago

    I take notes in Joplin with the command and a breakdown of any flags, parameters, etc, and what they everything means/does.

  • @wewbull@feddit.uk
    link
    fedilink
    English
    21 month ago

    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.

  • @redxef@feddit.org
    link
    fedilink
    English
    21 month ago

    I just keep my history file around and have set it up to never truncate. Then grep or ^R.

  • @torgeir@lemmy.ml
    link
    fedilink
    125 days ago

    I put mine as zsh autoloads. This way feels almost as light as creating aliases once set ut, and also allows for the scripts to have slow initializing code and still be readily available, without having to load everything immediately when zshrc loads and wait for it all the time, even when you might not need it.

  • Sonotsugipaa
    link
    fedilink
    English
    11 month ago

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