On Sat, Apr 13, 2019 at 09:28 Pierre Labastie <[email protected]> wrote:
> > Let me finish with this patch. I've managed to eliminate all the shellcheck > warnings, without exporting variables. I've added a couple of double > backslash's to silent the last ones (*). I'm running a build right now, to > check that everything is OK. > > Do you want to check the other scripts? Nothing mandatory, of course. I'll > be > glad to keep collaborating with you. > Either way works for me too. I’m happy to add some more, but won’t be able to get to it right away. I’ll check back in a day or two to see how it’s going. Pierre > (*): I'd never realized that: > $ echo -e "\n" > and: > $ echo -e "\\n" > were equivalent (print a blank line), while: > $ echo -e \n > and: > $ echo -e \\n > aren't (the first one prints a "n", the second one prints a blank line). I > begin to understand the use of "printf" builtin Yes, printf is more predictable. I try to use it instead of echo almost everywhere. I learned that from here: https://www.etalabs.net/sh_tricks.html JH
-- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
