> echo is okay if no literal `\` appears in its argument list.
> If one does, I need to switch to printf(1)
Wise advice that I'd modify only by s/okay/right/. I believe
I've never used printf(1), but if I were preparing tiny test
scripts for groff I might well do so.
Doug
On Thu Oct 10, 2024 at 1:22 AM CEST, G. Branden Robinson wrote:
> [...]
>
> The value of printf(1) lies not in its firepower (which is indeed
> supercharged for many [most?] shell applications) but its
> _predictability_.
>
> printf(1) is a POSIX invention because of an old BSD vs. System V
> confl
Hi Doug,
At 2024-10-09T18:48:11-0400, Douglas McIlroy wrote:
> > > "printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -mandoc -Z - "
> >
> > [...]
> > The foregoing is also revealing of a low level of sophistication with
> > printf(1).
>
> True. But why harness marginal feaures for such small benefi