Tekk has quit [Quit: zzz]
cve has quit [Remote host closed the connection]
cve has joined ##bash-crimes
Maja_ has joined ##bash-crimes
<
Maja_>
isabella: i'm a few days late to the party because my quassel shat the bed, but this is absolutely wonderful
<
isabella>
Glad you liked it lol
<
Maja_>
isabella: hm, can you actually call a function called function without special characters, though?
<
isabella>
You need to quote the word function
<
isabella>
"f"unction
<
isabella>
funct\ion
<
isabella>
function''
<
isabella>
Or you need to find a way to make it not a keyword
<
isabella>
Like a=b function
<
isabella>
I'm not sure if it's doable without special characters
<
Maja_>
in other news I've discovered oil shell
<
Maja_>
they claim to have a dialect compatible with bash et al
<
Maja_>
it's... pretty compatible
<
Maja_>
runs my impl of AES and x25519 correctly
<
Maja_>
but sha2 breaks with unexplained wrong outputs
<
Maja_>
regis: can't speak of the taste issue, but as written this won't run, iirc you need a space after the { and &
<
Maja_>
definitely would be cheesy if you ended up making such a mistake ;3
<
Maja_>
ah, only the one after { is mandatory, but you might as well go for symmetry
<
Maja_>
shout out to tio.run for being the easiest sandbox to use for testing this
https://tio.run/##S0oszvj/30pDs9qqxkqt1trq/38A
<
regis>
Maja_: Thanks. ZSH on FreeBSD works with no spaces but /bin/sh (non-GNU, not-bash stuff) indeed requires a space after "{"!
<
regis>
/bin/sh actually doesn't even allow me to overwrite built-in ":" function
<
regis>
but I can `alias :=false;:;echo $?` and get 1, lol
<
Maja_>
gah, those fuckers are trying to nerdsnipe me
<
Maja_>
hm, actually, why does read -u $fd exist when you can do read <&$fd
<
Maja_>
probably the latter didn't exist when they introduced it
cve has quit [Ping timeout: 252 seconds]