The \ problem (or annoyance), and a fix proposal

Duarte Cordeiro Duarte.Cordeiro at
Tue Jan 13 09:36:37 PST 2004


This problem seems common.

>From the book:
../glibc-2.3.2/configure --prefix=/tools \
--disable-profile --enable-add-ons \
--with-headers=/tools/include \
--with-binutils=/tools/bin \

And someone types it like this:
../glibc-2.3.2/configure --prefix=/tools \ --disable-profile
--enable-add-ons \ --with-headers=/tools/include \
--with-binutils=/tools/bin \ --without-gd
(all in one line, with the backslashes)

Although the backslash + space isn't a problem in any shell (or at least I
think it's not), the book should (IMHO) clarify why it's there, and when to
leave it out.

I haven't read the book too closely, but a search for "backslash" returns
only a result in the changelog section.

The recommendation:

  While you're at it (telling users to type commands by the book) explain to
them what's the backslash propose, and if they type the command all-in-one
line, that they need to remove it. I would put a reminder (like: remember,
if you type everything in one line, remove the backslashes) in the first 2
or 3 times in appears in the book.

It surely doesn't harm anyone, and it clarifies its use.

Hope I was helpfull,


PS: sorry for my lame english ;)

More information about the lfs-dev mailing list