Elektrine lite

← Feed

@thingsiplay@lemmy.ml

Post #2206250

2026-04-01 14:59 UTC

I do write scripts and commands (and Bash aliases or functions) all the time. The scripts live in ~/.local/bin and are executable like any other program, as that directory is in my PATH variable. I have a projects directory where I archive them, and some of them are uploaded to my Github account. Some of them are later rewritten in Python and get a life on its own. 1. [yt-dlp-lemon](https://github.com/thingsiplay/yt-dlp-lemon): Simple wrapper to yt-dlp with only a subset of options. 2. [unwrap](https://github.com/thingsiplay/unwrap): Wrapper to marry GNU Parallel and 7-Zip for archive extraction. 3. [biggest](https://github.com/thingsiplay/biggest): List biggest files and folders. 4. [?](https://gist.github.com/thingsiplay/69aada6a57f829d9580d7b54f8a207a0): cheat .sh - The only cheat sheet you need. (Note, commands name is just `?`) 5. [woman](https://gist.github.com/thingsiplay/f71383569c10da17f772b9967f5a5767): Preview list for man documents. Besides my more simple scripts and aliases and functions. :::spoiler 6. system `update` and all `updates`: ```bash alias update='eos-update --yay' alias updates='eos-update --yay ; flatpak update ; flatpak uninstall --unused ; rustup self update ; rustup update' ``` ::: :::spoiler 7. Or a recent script to convert files to mp3 format: `tomp3` ```bash #!/usr/bin/env bash for file in "${@}"; do output="${file%.*}.mp3" if [[ -f "${output}" ]]; then continue fi ffmpeg -i "${file}" -b:a 320k "${output}" done ``` :::

Replies (1)

  • @fozid@feddit.uk 2026-04-01 17:47

    That's so clever yet so simple, keep all the scripts in folder that's in PATH. I will deffo use that idea instead of a dedicated folder called scripts in my home folder.

    Open ##2206263