Re: [Mutt] #3386: search in body searches raw base64 stream instead of decoding it

To: cypher@xxxxxxxxxxxxxx, dan@xxxxxxxxxxxxxxxxxx, vincent@xxxxxxxxxx
Subject: Re: [Mutt] #3386: search in body searches raw base64 stream instead of decoding it
From: Mutt <fleas@xxxxxxxx>
Date: Wed, 24 Feb 2010 20:20:40 -0000
Auto-submitted: auto-generated
Cc: mutt-dev@xxxxxxxx
In-reply-to: <042.92c5433c0e60beb4af175a6cfb884f7c@xxxxxxxx>
List-post: <mailto:mutt-dev@mutt.org>
List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-dev"
Mail-followup-to: fleas@xxxxxxxx
References: <042.92c5433c0e60beb4af175a6cfb884f7c@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

#3386: search in body searches raw base64 stream instead of decoding it
------------------------+---------------------------------------------------
 Reporter:  cypherpunk  |       Owner:  mutt-dev
     Type:  defect      |      Status:  new     
 Priority:  major       |   Milestone:          
Component:  mutt        |     Version:  1.5.20  
 Keywords:              |  
------------------------+---------------------------------------------------

Comment(by cypherpunk):

 Indeed, setting thorough_search solves this. I strongly agree that "yes"
 is the sensible "do what the user expects" default.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3386#comment:5>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

References:
- [Mutt] #3386: search in body searches raw base64 stream instead of decoding it
  - From: Mutt

Prev by Date: Re: [Mutt] #3386: search in body searches raw base64 stream instead of decoding it
Next by Date: Re: [Mutt] #3386: search in body searches raw base64 stream instead of decoding it
Previous by thread: Re: [Mutt] #3386: search in body searches raw base64 stream instead of decoding it
Next by thread: Re: [Mutt] #3386: search in body searches raw base64 stream instead of decoding it
Index(es):
- Date
- Thread