Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 15-Jan-2025 14:00:48 JST Haelwenn /элвэн/ :triskell:

   • wyatt
   @mirabilos @wyatt Well getting an error on no match is in fact one of the things I like about ed and hate the lack of it in sed.
   
   As for binary-safe… wouldn't sed also have this kind of problem depending on the implementation?
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 15-Jan-2025 14:12:44 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • wyatt
     @wyatt @mirabilos Searching in https://pubs.opengroup.org/onlinepubs/9799919799/utilities/ed.html for "newline" it doesn't seems like ed needs to need to always add a final newline.
     
     So I'm taking that specific part as implementations liberties, like GNU or *BSD ed(1) doing it even though they don't need to.
   • Embed this notice
     wyatt (wyatt@soc.megatokyo.moe)'s status on Wednesday, 15-Jan-2025 14:12:48 JST wyatt

     in reply to
     @lanodan @mirabilos i need to look at POSIX specs but i'm pretty sure sed doesn't putchar('\n') when it hits EOF