[FM Discuss] command line manual - please have a squiz

[Luka Frelih]

heya!

great book, nice catch fixing the pre bold font.

on page 77 (advanced  part toc) gnu screen lost the space between words

in regexp chapter, "fuzzy matching" is used where i guess "pattern 
matching" is more appropriate.
i understand fuzzy to mean approximate matching, using soundex or 
levenshtein distances to find similar strings, like in typo correction 
or spellchecking.

perhaps it would be nice to mention the rpl command in the sed chapter? 
i know it's not installed by default but it's a more user friendly way 
to perform basic search and replace, which is usually the first reason 
to use sed in a command line

also not sure why (looks like some font encoding foo?) but try 
copy-pasting everything from evince to a text editor. i get mostly a lot 
of greek-letter garbage. this also makes searching in the manual find 
only things in courier.

best,
LF

adam hyde wrote:
> soooo....the rather amazing command line manual is pretty much good to
> go...we will send to the FSF and they will print 200 and give us the $
> which in turn goes towards another collab sprint with the FSF...
>
> there has been some amazing contribs to this manual and no little thanks
> to andy for being the master maintainer for the manual...it looks and
> reads fantastico!
>
> there is a copy of the pdf here:
> http://adam.engagetv.com/cli/
>
> this will go to the printer. there might be a few tweaks, but this is
> pretty much it
>
> last call for feedback...
>
> adam
>
>
>
>
>