Jean-Philippe MENGUAL wrote:
> oops sorry, I'm very exhausted :D I didn't give you the proper line.
> This I gave is, of course, necessary. The mistake is in: find . -name
> \*.html -type f -exec cp -v \{} /usr/share/doc/mpfr-&mpfr-version;
> \;</userinput></screen>
>
> The problem is the \ before {} (\{}). Not bug but to learn it's not
> exact. The line should be: find . -name \*.html -type f -exec cp -v
> {} /usr/share/doc/mpfr-&mpfr-version; \;</userinput></screen>
Well it's not, strictly speaking, wrong, but you are right that it is
redundant for bash. I'm not sure it it's redundant or not for other
versions of sh, e.g. dash.
The . after find is also redundant.
When a user is learning, he should ask "what does that do". Looking at
the bash man page shows:
A non-quoted backslash (\) is the escape character. It preserves the
literal value of the next character that follows, with the exception of
<newline>.
That really should be sufficient. I don't think this rises to the level
where the book needs to be changed.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
