int*dmi;*dmi=0 // --> WHY2025Jun 27

#ScriptSaturday with enough alias magic, bash can have real try-catch syntax!

libsh module here; BSD-3 :)

Show threadWolf480plJun 27
@domi wait, but it only actually catches if you wrap it in a subshell, otherwise it just exits the whole shell after executing the catch and finally blocks?
Show threadint*dmi;*dmi=0 // --> WHY2025Jun 27
@wolf480pl sorry i copied the wrong snippet, it’s fixed now
Show threadWolf480pl

@domi oh, ok.

hmm... wouldn't it make more sense to set the trap inside the subshell?

Jun 27 at 11:05pmWeb
Show threadint*dmi;*dmi=0 // --> WHY2025Jun 27
@wolf480pl required some fiddling, but done! I could move essentially everything into that subshell, but i’m gonna leave out the other functions for now for slightly better readability
Show threadWolf480plJun 27

@domi does that mean one can now

try (
try (
return 1
) catch (
echo catch 1
) yrt
) catch (
echo catch 2
) yrt

?

Show threadint*dmi;*dmi=0 // --> WHY2025Jun 27

@wolf480pl jesus christ

wrong braces, but. maybe? i’m gonna check

Show threadWolf480plJun 27
@domi wrong braces on purpose, otherwise I'm gonna redefine _catch :(
Show threadint*dmi;*dmi=0 // --> WHY2025Jun 27

@wolf480pl okay, nesting is broken. i tried restructuring more stuff into the subshell and it “works” but some catches get redefined as the generic one

i’ll work on it more tomorrow :)

Show threadWolf480plJun 28
@domi actually, my example is stupid because the correct behaviour is only "catch 1" and it's indistinguishable from the outer catch getting overwritten. I should've used finally.
Show threadWolf480plJun 28
@domi oh and to be clear: I'm not likely to actually use this, I'm just nerdsniping you :P
Show threadWolf480plJun 28
@domi i do think it's cool tho
Show threadint*dmi;*dmi=0 // --> WHY2025Jun 28

@wolf480pl the horrifying part is that this provides enough utility that I may want to use it! and this only started as a “what if?” :D

nerdsnipes are appreciated. i don’t have anyone else do code review, so this is nice