Conversation

Notices

1. Embed this notice
   :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Thursday, 28-Sep-2023 11:41:02 JST :apa: スプリットショックウイルス †

   • かき@GNUsocialJP
   • :netbsd: Nishi
   # for i in $(ls update_scripts/ ) ; do echo './update_scripts/$i &' >> start.sh ; done
   Illegal variable name.
   

   cc @nishi explain

   • Embed this notice
     :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans: (allison@hidamari.apartments)'s status on Thursday, 28-Sep-2023 11:41:00 JST :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:

     in reply to

     • :netbsd: Nishi
     @splitshockvirus @nishi wasn't csh first written before posix and thus decided to deviate in behavior wherever the implementers saw fit?
   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Thursday, 28-Sep-2023 11:41:01 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP
     • :netbsd: Nishi

     @nishi

     Ayo I still want answers, why is csh not POSIX compliant? Don't tell for loops are bloat cause that's bullshit.

   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Thursday, 28-Sep-2023 11:41:02 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP
     • :netbsd: Nishi

     @nishi

     # echo $0
     -csh
     

     Oh I figured it out it's cause I'm using csh. That's extremely nasty turn tha shit off.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans: (allison@hidamari.apartments)'s status on Thursday, 28-Sep-2023 11:46:54 JST :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:

     in reply to

     • :netbsd: Nishi
     @splitshockvirus @nishi Because FreeBSD takes legacy very seriously. I forget what NetBSD's default is, but OpenBSD neatly sidesteps it by using pdksh as their default.
   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Thursday, 28-Sep-2023 11:46:56 JST :apa: スプリットショックウイルス †

     in reply to

     • かき@GNUsocialJP
     • :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:
     • :netbsd: Nishi

     @allison @nishi

     That would stand to reason. But holy shit why would 13.2 put this as the default shell? I'd take regular sh over this.

   • Embed this notice
     :netbsd: Nishi (nishi@hkgk.nishi.boats)'s status on Thursday, 28-Sep-2023 11:47:42 JST :netbsd: Nishi

     in reply to

     • :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:
     @allison @splitshockvirus netbsd default is ash
     :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans: likes this.
   • Embed this notice
     :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans: (allison@hidamari.apartments)'s status on Thursday, 28-Sep-2023 11:47:49 JST :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:

     in reply to

     • :netbsd: Nishi
     @nishi @splitshockvirus Another sensible choice.