Conversation

Notices

1. Embed this notice
   silverwizard (silverwizard@convenient.email)'s status on Monday, 03-Feb-2025 23:54:36 JST silverwizard

   Its been a long time since someone wrote shell unportable enough to ruin my day.

   If you're gonna use bashisms, don't just huck them into `/bin/sh`

   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Monday, 03-Feb-2025 23:56:02 JST silverwizard

     in reply to

     I guess technically they ran:
     

     sh `#!/bin/bash;if [[ "$FOO" == BAR && "$BAZ" = BLEEN ]]; then;echo true;else;echo false;fi

     Which implies they knew it was base and not just raw shell?

   • Embed this notice
     Fear and Tooting in Las Vegas (steevmi1@freeradical.zone)'s status on Tuesday, 04-Feb-2025 00:00:57 JST Fear and Tooting in Las Vegas

     in reply to

     @silverwizard When I get weird "I don't understand why this isn't working correctly" I flip the interpreter to bash and retest, and more often then not angrily mutter "I can walk! It's a Christmas Miracle! Thank you officers!"

   • Embed this notice
     silverwizard (silverwizard@convenient.email)'s status on Tuesday, 04-Feb-2025 00:00:57 JST silverwizard

     in reply to

     • Fear and Tooting in Las Vegas
     @steevmi1 yeah! I know right! The problem with bashisms isn't that they're wrong, it's just that they're weird enough to teach bad habits