Re: index_format and <bar> vs <space>, segment fault
Thank you for your reply. It will takes me some time to test your suggestion.
For the following question,
" How did you manage to quote it without segfault: <list-reply>
directly from index?"
the answer is YES. Because at this time, the message is relayed to
the Editor VIM, no problem appeares.
Ye Fei
On 2006-06-15, Alain Bench (veronatif@xxxxxxx) wrote:
> Hello,
>
> On Monday, June 12, 2006 at 9:02:21 +0200, Ye Fei wrote:
>
> > When reading Rado's message, my Mutt (Mutt 1.5.11+cvs20060403) stops
> > working. It quits with a segment fault.
>
> Take a look at the yet unsolved Debian Bug#339555 "Segmentation
> fault when displaying a iso8859-1 mail header" to study if that's the
> same thing. Especially check first the gdb backtrace.
>
>
> > some "characters" which can not be treated correctly by mutt in the
> > zh_CN.GBK locale.
>
> Only a small minority of the Latin-1 chars of Rado's table are
> displayable in a GBK locale. Mutt is able to display them, and masks
> other ones with a question mark. That's the best you can have, unless
> you change to a better terminal and locale, or use //TRANSLITerations.
>
>
> > The original message by Rado is attached below.
>
> How did you manage to quote it without segfault: <list-reply>
> directly from index?
>
>
> >| LANGUAGE=en_CN:en_US:en_GB:en:zh_CN
>
> BTW: Unset it (unless you have a good reason).
>
>
> >| set charset="gbk"
>
> Drop it.
>
>
> >| charset-hook ^gb2312$ gbk
>
> Are you sure this really makes sense?
>
>
> >| charset-hook ^iso-8859-1$ gbk
> >| charset-hook !utf-8 gbk
>
> Whatever intent you had, this looks to me like self-foot-shooting,
> twice ;-). All incoming mails (outside of UTF-8 ones) are treated as if
> they contained GBK. Which would be fine, if all mails really contained
> GBK. But when mails contain whatever else, this gives you garbage.
> Better drop both lines, and review original intent searching another
> solution with fewer drawbacks.
>
>
> Bye! Alain.
> --
> When you want to reply to a mailing list, please avoid doing so with
> Lotus Notes 5. This lacks necessary references and breaks threads.