<<< Date Index >>>     <<< Thread Index >>>

Re: [tbm@xxxxxxxxxx: Bug#301448: should decode mail before text



Bonjour Vincent!

 On Monday, March 28, 2005 at 2:32:17 PM +0200, Vincent Lefèvre wrote:

> Is there any reason why [$thorough_search] is set to "no" by default?
> Any drawback setting it to "yes"?

 · Would break legacy behaviour.

 · More power consumption.

 · Can surprise user by unexpected prompt for a passphrase.


    OTOS what an average user expects from search is obviously the
$thorough_search=yes behaviour. More: The average user can't even
imagine it is possible search works so poorly as it works by default,
failing to find umlauts when message and term are different charsets,
failing to find words in encoded or encrypted messages, und so weiter.
This can lead to difficult to track errors, possibly with grave
consequences, such as untriggered hooks. And when it remains apparently
random and unexplainable, let some people feel Mutt is just unreliable.


    I use $thorough_search=yes always, and unset it temporarily only
when I want to specifically locate raw Lef=E8vre. My humble: Change
default, and remove var.


Bye!    Alain "radical" Bench.
-- 
set honor_followup_to=yes in muttrc is the default value, and makes your
list replies go where the original author wanted them to go: Only to the
list, or with a private copy.