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

[Andy Oram]

I look forward to the improvements listed below. But don't throw out the word "fuzzy" entirely. I want terms that mean something to average readers. They won't immediately understand what you mean by "pattern" (it has innumerable meanings in everyday life and compute science). The reader for this book, if I have the right image of the reader, won't connect "fuzzy" with the academic use by search technologists. But its use in the chapter could be reduced.

Andy

----- Original Message -----
From: "adam hyde" <adam at flossmanuals.net>
To: discuss at lists.flossmanuals.net
Sent: Thursday, April 9, 2009 10:59:30 AM GMT -05:00 US/Canada Eastern
Subject: Re: [FM Discuss] command line manual - please have a squiz

On Thu, 2009-04-09 at 16:48 +0200, Luka Frelih wrote:
> 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
>