Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 27-Sep-2024 00:57:50 JST Haelwenn /элвэн/ :triskell:

   • Rich Felker
   • Orman
   @dalias @orman In fact, I think error messages for less technical people should be a bit more verbose.
   
   Like someone technical can understand ENOENT but "No such file or directory" should be preferred (and the message ought to tell which file/directory wasn't found).
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 27-Sep-2024 01:29:59 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Rich Felker
     • Orman

     @dalias @orman Meanwhile "show more" makes sense for logs of verbose/debug messages that you usually don't need unless there is some kind of problem.
     And getting the last line(s) of said messages always displayed can be nice so you know what was done prior to a freeze.

   • Embed this notice
     lily ?️‍⚧️ (tauon@possum.city)'s status on Saturday, 28-Sep-2024 00:50:06 JST lily ?️‍⚧️

     in reply to

     • Rich Felker
     • Orman

     @lanodan@queer.hacktivis.me @dalias@hachyderm.io @orman@furry.engineer exactly! my error messages are usually written like cannot open /Users/lily/Docuemnts/file.txt: No such file or directory (os error 2), which:
     - says which file failed
     - says why it failed (no such file or directory, not, say, permission denied)
     - gives the errno (for nerds)

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 28-Sep-2024 00:58:16 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Rich Felker
     • lily ?️‍⚧️
     • Orman

     @tauon @dalias @orman I could consider giving the errno (specially once I add locales) but to give an example of what I do here:
     cat: error: Failed opening file '/home/haelwenn/foobar': No such file or directory

     • name of the tool (useful for logs)
     • error/warning/… clearly labelled (and reusing the error: pattern from compilers)
     • quotes around user input (here the path), although I'd consider putting it at the end so no they wouldn't be needed anymore but sometimes there's two arbitrary parts (like when copying)