r_bash – Telegram
Dynamic Motd (Message of the Day)
https://redd.it/1jvfhui
@r_bash
Function to generate images with Gemini

https://preview.redd.it/ysghltkzxvte1.png?width=1408&format=png&auto=webp&s=fdbeb494d3dcc063f2314e8c93aaa2f0c25be10b

$ declare -f imagen
imagen ()
{
curl -s https://generativelanguage.googleapis.com/v1beta/models/imagen-3.0-generate-002:predict?key=$GEMINIAPIKEY -H 'Content-Type: application/json' -X POST -d '{"instances": {"prompt": "'"$1"'"},"parameters": {"sampleCount": 1, "aspectRatio": "16:9"}}' | jq -r '.predictions0.bytesBase64Encoded' | base64 -d > "$2.png"
}

$ imagen "A gorilla surfing near the beach" gorilla

$ file gorilla.png
gorilla.png: PNG image data, 1408 x 768, 8-bit/color RGB, non-interlaced

https://redd.it/1jvinxe
@r_bash
Reading then writing the same file empties it

I have a noscript and when running it ./noscript >~/.config/chkupdates/chkupdates.conf ($conf in the noscript), I'm not sure why the output isn't overwriting the file with what shows in stdout--the file is instead cleared with a newline.

If I ./noscript >/tmp/test, I can see the expected output is saved to this arbitrary file, so something appears to be wrong with streaming the data and overwriting to $conf.

The noscript reads $conf, so I already made efforts to have the noscript reads this file in a loop which then outputs to a $tmpfile which the noscript print the $tmpfile's contents so that the user can pipe it out to $conf safely.

https://redd.it/1jvgvg5
@r_bash
Can't seem to find decent commenting style

I want first comment (first line) to describe the entire group of code, second comment (second line) to describe only first line of code starts with `tracked=`. How to best make this more obvious? The second comment is too long to fit on the same line as the code.

# skip parsing to print full line when a line doesn't start with
# trim leading whitespaces. Ref:
# https://web.archive.org/web/20121022051228/http://codesnippets.joyent.com/posts/show/1816
tracked="${tracked#"${tracked%%[![:space:]]*}"}"
if [[ "$tracked" =~ ^[^[:alnum:]] ]]; then
echo "$tracked"
continue
fi

And in general, I'm not sure there's much decent logic at all to have a comment represent more than one block of code (it might imply multiple blocks, but how do you know when it should end)? Having an end marker comment seems excessive considering I never really come across it.

Probably more of a general coding question, looking for a solution that can work across multiple languages.

https://redd.it/1jvdhmr
@r_bash
Actual Vim Motions in bash?

I only found like two posts on reddit and another on StackOverFlow where the user is expressing frustration of set -o vi and seeking an alternative approach to get vim motions in his shell, which is very shocking to me but maybe I just suck at googling right? or people know their shell keybinings unlike me - lazy to learn something new. Anyway, I found this project which pulls it off: https://github.com/akinomyoga/ble.sh
The problem though is that there's noticeable latency that I can't wrap my head around, so if someone uses this and it doesn't have latency please tell me what terminal emulator you use.

https://redd.it/1jwrevg
@r_bash
I need to know why this works.

Why does this function preserve the arg escaping correctly? I sorta get it, and I sorta don't. Is there a better way to do this that works in posix sh like this does?

All the explanations written in the PR are by me, they represent my current understanding, as are the explanations underneath the shellcheck disables.

Is my understanding correct?


    arg2list() {
local toset=$1
shift 1
# shellcheck disable=SC2145
# we actually want to eval on structured data.
# so mixing strings with arrays is the point
# shellcheck disable=SC2294
# and yes eval on a string negates the benefits of arrays,
# thats why we leave it an array.
eval "$toset=($@)"
}


Used in this function, which generates C code to stdout

$1 and $2 are a space separated string, of all things passed in to the noscript with --add-flags theval concatenated with spaces

    addFlags() {
local n flag before after var

# Disable file globbing, since bash will otherwise try to find
# filenames matching the the value to be prefixed/suffixed if
# it contains characters considered wildcards, such as `?` and
# `*`. We want the value as is, except we also want to split
# it on on the separator; hence we can't quote it.
local reenableGlob=0
if [[ ! -o noglob ]]; then
reenableGlob=1
fi
set -o noglob
# shellcheck disable=SC2086
arg2list before $1
# shellcheck disable=SC2086
arg2list after $2
if (( reenableGlob )); then
set +o noglob
fi

var="argv_tmp"
printf '%s\n' "char **$var = calloc(${#before[@]} + argc + ${#after[@]} + 1, sizeof(*$var));"
printf '%s\n' "assert($var != NULL);"
printf '%s\n' "${var}[0] = argv[0];"
for ((n = 0; n < ${#before[@]}; n += 1)); do
flag=$(escapeStringLiteral "${before[n]}")
printf '%s\n' "${var}[$((n + 1))] = \"$flag\";"
done
printf '%s\n' "for (int i = 1; i < argc; ++i) {"
printf '%s\n' " ${var}[${#before[@]} + i] = argv[i];"
printf '%s\n' "}"
for ((n = 0; n < ${#after[@]}; n += 1)); do
flag=$(escapeStringLiteral "${after[n]}")
printf '%s\n' "${var}[${#before[@]} + argc + $n] = \"$flag\";"
done
printf '%s\n' "${var}[${#before[@]} + argc + ${#after[@]}] = NULL;"
printf '%s\n' "argv = $var;"
}


Context
https://github.com/NixOS/nixpkgs/pull/397604


I have tried a ton of ways to do this.

I have tried for arg in "$@"; do for example, but was unable to get that to work.

So why does this work? Can it be improved? This is the only approach I have succeeded with so far.

https://redd.it/1jx8dmm
@r_bash
Replacing echo with printf broke my noscripts

Taking the advice in https://www.reddit.com/r/bash/comments/1519wby/why\_printf\_over\_echo\_noob\_question/ and elsewhere, I proceeded to do

sed -i 's/echo /printf \x27%s\\n\x27 /' bin/*.sh

Whereas echo had worked perfectly, many strings now mysteriously got truncated. I reverted back to echo and all is working well, again, but I'm intrigued why this happened. I tried replacing %s with %b but it made no difference.

Does printf %s not handle utf-8 correctly or something?

https://redd.it/1jxi95b
@r_bash
Why does this work?

    arg2list() {
local toset=$1
shift 1
# shellcheck disable=SC2145
# we actually want to eval on structured data.
# so mixing strings with arrays is the point
# shellcheck disable=SC2294
# and yes eval on a string negates the benefits of arrays,
# thats why we leave it an array.
eval "$toset=($@)"
}


Used in this function, which generates C code to stdout

    addFlags() {
local n flag before after var

# Disable file globbing, since bash will otherwise try to find
# filenames matching the the value to be prefixed/suffixed if
# it contains characters considered wildcards, such as `?` and
# `*`. We want the value as is, except we also want to split
# it on on the separator; hence we can't quote it.
local reenableGlob=0
if [[ ! -o noglob ]]; then
reenableGlob=1
fi
set -o noglob
# shellcheck disable=SC2086
arg2list before $1
# shellcheck disable=SC2086
arg2list after $2
if (( reenableGlob )); then
set +o noglob
fi

var="argv_tmp"
printf '%s\n' "char **$var = calloc(${#before[@]} + argc + ${#after[@]} + 1, sizeof(*$var));"
printf '%s\n' "assert($var != NULL);"
printf '%s\n' "${var}[0] = argv[0];"
for ((n = 0; n < ${#before[@]}; n += 1)); do
flag=$(escapeStringLiteral "${before[n]}")
printf '%s\n' "${var}[$((n + 1))] = \"$flag\";"
done
printf '%s\n' "for (int i = 1; i < argc; ++i) {"
printf '%s\n' " ${var}[${#before[@]} + i] = argv[i];"
printf '%s\n' "}"
for ((n = 0; n < ${#after[@]}; n += 1)); do
flag=$(escapeStringLiteral "${after[n]}")
printf '%s\n' "${var}[${#before[@]} + argc + $n] = \"$flag\";"
done
printf '%s\n' "${var}[${#before[@]} + argc + ${#after[@]}] = NULL;"
printf '%s\n' "argv = $var;"
}


Context
https://github.com/NixOS/nixpkgs/pull/397604


https://redd.it/1jx8bta
@r_bash
BASHAM! : A Simple Bash Script to Manage Your Assembly Projects.

I've been fooling away my days by doing my hobbies. I was supposed to learn assembly but my idiotic ass learnt bash noscripting instead. At least I can still learn assembly a bit with it...


BASHAM!

Yeah, that's the repo. I'm looking for attention so I get some more contributors... 🫤

https://redd.it/1jynn7o
@r_bash
check if entry is in Array for If Statement

Hi,


New to bash so still trying to understand how to do everything, but in the process of writing a simple backup noscript, now I need to expand it to use an array for the exclusion folder(s) and to get the if statement to ignore any folder in the array.

Can anyone help.

Thanks,


#!/bin/bash



# variables

SOURCE="/volume1/docker/"

DEST="/volume1/Backups/Docker-Backups/"

DATE=$(date +%Y%m%d_%H%M%S)

# EXCLUDE="dir1"

EXCLUDE = ("dir1" "dir2" "dir3")



#change to folder to backup from

cd $SOURCE



# iterate over subdirectories

for subdir in */; do

#Extract dir name

dirname=$(basename "$subdir")



# zip dir

# need to convert to use array

if [[ "$dirname" != "$EXCLUDE" ]];

then

zip -r "$DEST$dirname $DATE.zip" "$subdir"

fi

done



# delete old backup files

find $DEST* -mtime +7 -exec rm {} \;

https://redd.it/1jz387b
@r_bash
Do you unit test your Bash noscripts? If so, how?

Curious if anyone here uses a proper testing framework like bats or rolls their own setup? Or do you some set -euo pipefail, and hope for the best 😅

Scripts running in prod always welcome extra paranoia.

https://redd.it/1jzywm5
@r_bash
Is it possible to write a bash noscript that installs python automatically?

I'm developing a YouTube File Manager with python although I need a way for my fellow YouTubers to use it. Unless if there is a way to turn it into an executable version in all operating systems?

https://redd.it/1k0ilyw
@r_bash
Is this still valid for you in 2025?
https://redd.it/1k16lvl
@r_bash
What's the most "overkill but it works" bash noscript you've written?

Sometimes I catch myself writing 100-line bash noscripts for things that could probably be done in 5 lines with another tool... but where’s the fun in that?

Curious what ridiculous but functional bash noscripts you've created that made you go: "this is fine."

https://redd.it/1k1c9vg
@r_bash
Linux mint cinnamon

I have a school project and they've asked for a few screenshots showing the use of commands to create a tutorial book.
Commands like creating a file, then transferring the file to a different directory.
Everyone I attempt to use the command lines it doesn't work. I've looked up command "cheat sheets" I feel like I'm missing something

https://redd.it/1k1lxu9
@r_bash
How many REAL MEN are there out there who think sudo is for pussies and just do everything as root?

I can't be the only one.

https://redd.it/1k1tygt
@r_bash