News for hackers. Stuff that matters.

uplime

Re:Coreutils Gotchas (2015) on Friday June 18, 2021 @05:31PM (#27555260)
> You seem to have a very narrow definition of "portable."

Can you explain how wanting to include more programs into the definition of portable is narrow?

> Can you link to the definition of the jargon term you appear to be using here?

The same definition I've always seen in every community discussing shell-scripting: if it's specified by the POSIX (Portable Operating System Interface) standard. POSIX does have a definition of `echo`. GNU echo does not conform to it by default, but can be configured to.

> Also, have you considered that some words have colloquial meanings too, and that it doesn't make sense to label them as "not correct"?

But it makes sense to label `echo` itself as not portable? The argument can be made that `GNU echo` is not portable (even though it can be with an environment variable), however that should be specified, instead of mentioning there are several implementations where it is non-standard.

Re:Coreutils Gotchas (2015) on Friday June 18, 2021 @03:32PM (#27553995)
You can with the POSIXLY_CORRECT environment variable:

$ /bin/echo --version echo (GNU coreutils) 8.30 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

Written by Brian Fox and Chet Ramey. $ POSIXLY_CORRECT=1 /bin/echo -e -e

Which is why I say relying on `echo` is fine, since its standard. Relying on `echo` to use options is not. That's also why the author is correct that you should use `printf`, because POSIXLY_CORRECT is not set, then you can run into non-standard behavior, like you showed.

Re:Coreutils Gotchas (2015) on Friday June 18, 2021 @03:03PM (#27553716)
It makes relying on meaningful options passed to `echo` non-portable. You can always rely on `echo` being on the system (thanks to POSIX), which is what makes it portable. Relying on the behavior of -e/-n/etc is not.
Re:Coreutils Gotchas (2015) on Friday June 18, 2021 @02:53PM (#27553602)
GNU coreutils isn't a standard. It conforms to and extends the POSIX standard. If it was just talking about GNU echo, then that `echo` would work the same on every machine. It even explicitly mentions other `echo` implementations, like the shell builtins. `echo` itself is portable, none of its flags are.
Re:Coreutils Gotchas (2015) on Friday June 18, 2021 @01:10PM (#27552542)
It probably is what they meant. However, what was written is that `echo` itself is non-portable, which isn't correct.
Re:Coreutils Gotchas (2015) on Friday June 18, 2021 @01:05PM (#27552488)
> echo is non portable and its behaviour diverges between systems and shell builtins

`echo` is portable: https://pubs.opengroup.org/onlinepubs/009695399/utilities/ec... Any options passed to `echo` are not. Although I agree `printf` should be used instead.