Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 26-Jan-2025 20:14:32 JST Haelwenn /элвэн/ :triskell:

   • ari :prideified:
   • Tulip ?️‍⚧️
   • anna
   • kimapr

   @kimapr @domi @ar @multisn8 @navi > POSIX sh doesn't even have a way to read a NUL-terminated string from a stream

   IIRC while IFS='' read do; …; done should be able to deal with null-separation fine and POSIX.1-2024 added null handling to several utilities.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 26-Jan-2025 21:15:43 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • ari :prideified:
     • Tulip ?️‍⚧️
     • anna
     • kimapr
     @kimapr @domi @ar @multisn8 @navi Well POSIX.1-2024 is pretty much real to me already, dash specifically needs to catchup but that's pretty much my entire experience of dash even before POSIX.1-2024 got released (same thing with busybox as a whole…).
     
     Although I prefer to keep using the previous version of POSIX for now but to me it's kind of like compatibility with debian stable rather than current systems, it's nice but not really a dealbreaker to pull something more recent.
   • Embed this notice
     kimapr (kimapr@ublog.kimapr.net)'s status on Sunday, 26-Jan-2025 21:15:46 JST kimapr

     in reply to

     • ari :prideified:
     • Tulip ?️‍⚧️
     • anna
     @lanodan @domi @ar @multisn8 @navi the IFS thing isn't really useful here* - read still reads newline-terminated lines, and i don't even want to do word splitting which is what IFS controls. what i want is `read -d '' line` to read a NUL-terminated "line" - this is real in bash and zsh but POSIX defines no useful options for read so dash doesn't have it either.
     
     I looked it up and they actually added -d to read in POSIX.1-2024! can't wait for it to become real
     
     * apparently it is, read trims trailing and leading whitespace if IFS is not set to '' which would break my script if it was passed filenames with that stuff which is definitely something i'd do, alongside putting newlines in filenames. i didn't catch this bug because none of the files i used had trailing or leading whitespace in there names