Graham Percival <[email protected]> writes:
> On Wed, Mar 14, 2012 at 10:27:52PM +0100, David Kastrup wrote:
>> And the MacOSX /bin/sh is the first shell I heard of that does not grok
>> echo -n.
>
> ...
>> If this may not be true, `printf' is in general safer and easier
>> to use than `echo' and `echo -n'.
>
> This matches the open group specifications.
>
> http://pubs.opengroup.org/onlinepubs/009695399/utilities/echo.html
>
> ...
> APPLICATION USAGE
>
> It is not possible to use echo portably across all POSIX
> systems unless both -n (as the first argument) and escape
> sequences are omitted.
Actually:
git grep "echo -n"
make/midi-rules.make: (echo '\header {'; for f in $(HEADER_FIELDS); do echo -n
mf/GNUmakefile: echo -n 'emmentaler-brace' > $@
scripts/build/install-info-html.sh:echo -n "$name: Writing index: $index_file...
smart-autogen.sh:echo -n $AUTOGEN_INPUT_CHECKSUM > $CHECKSUM_FILE
smart-configure.sh:echo -n $CONFIGURE_CHECKSUM > $CONFIGURE_CHECKSUM_FILE
stepmake/bin/stepmakeise.sh: echo -n "Checking version..."
stepmake/bin/stepmakeise.sh: echo -n "Checking latest..."
stepmake/bin/stepmakeise.sh: echo -n "Updating StepMake..."
stepmake/bin/stepmakeise.sh:echo -n "Stepmakeising..."
Wonderful.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
