Re: [Mutt] #2990: mutt-1.5.16: utf-8 support broken somewhere

#2990: mutt-1.5.16: utf-8 support broken somewhere between 1.5.13 and 1.5.16 Comment (by pdmef): First, can you please make sure to reply to ticket #2990 only and not open new ones like #2991? Second, what exactly doesn't work and what are the symptoms? Also, you might want to check the fil

mutt: 4 new changesets

4 new changesets in mutt: http://dev.mutt.org/hg/mutt/rev/96f931ae0b22 changeset: 5311:96f931ae0b22 branch: HEAD tag: tip user:Rocco Rutte <[EMAIL PROTECTED]> date:Tue Nov 20 19:46:52 2007 +0100 summary: Document that save-hook/fcc-hook/fcc-save-hook use $index_f

Re: [Mutt] #2991: Re: mutt-1.5.16: utf-8 support broken somewhere

#2991: Re: mutt-1.5.16: utf-8 support broken somewhere between 1.5.13 and 1.5.16 Changes (by pdmef): * status: new => closed * resolution: => duplicate Comment: Duplicate of #2990. -- Ticket URL:

Re: [Mutt] #2990: mutt-1.5.16: utf-8 support broken somewhere

#2990: mutt-1.5.16: utf-8 support broken somewhere between 1.5.13 and 1.5.16 Comment (by Sven Utcke): {{{ Hello pdmef, > First, can you please make sure to reply to ticket #2990 only and not open > new ones like #2991? Well, sorry about that, I sent the second mail before the ticket was

Re: [Mutt] #2990: mutt-1.5.16: utf-8 support broken somewhere

Hi, * Mutt wrote: Second, what exactly doesn't work and what are the symptoms? If receiving mail containing utf-8 encoded German umlauts (but presumably this applies at least to all iso-latin-1 letters) in either header or body everything looks as expected up to 1.5.14 (i.e. I see the actua

Re: [Mutt] #2990: mutt-1.5.16: utf-8 support broken somewhere

#2990: mutt-1.5.16: utf-8 support broken somewhere between 1.5.13 and 1.5.16 Comment (by Rocco Rutte): {{{ Hi, * Mutt wrote: >> Second, what exactly doesn't work and what are the symptoms? > If receiving mail containing utf-8 encoded German umlauts (but > presumably this applies at leas

Re: [Mutt] #2990: mutt-1.5.16: utf-8 support broken somewhere

#2990: mutt-1.5.16: utf-8 support broken somewhere between 1.5.13 and 1.5.16 Comment (by Sven Utcke): {{{ Hello Mutt, > >> Second, what exactly doesn't work and what are the symptoms? > > > If receiving mail containing utf-8 encoded German umlauts (but > > presumably this applies at le

Re: [Mutt] #2990: mutt-1.5.16: utf-8 support broken somewhere

Hi, * Mutt wrote: Can you please give the following information: the output of 'locale' On the currently used computer I get has6121h>/.../utcke% locale LANG=en_US LC_CTYPE="en_US" LC_NUMERIC="en_US" LC_TIME="en_US" LC_COLLATE="en_US" LC_MONETARY="en_US" LC_MESSAGES="en_US" LC_PAPER="en

Re: [Mutt] #2990: mutt-1.5.16: utf-8 support broken somewhere

#2990: mutt-1.5.16: utf-8 support broken somewhere between 1.5.13 and 1.5.16 Comment (by Rocco Rutte): {{{ Hi, * Mutt wrote: >> Can you please give the following information: the output of >> 'locale' > On the currently used computer I get > has6121h>/.../utcke% locale > LANG=en_US

[PATCH] Don't ignore $from in batch send mode

Hi, since changeset 5188, $from variable is not used in batch send mode. # HG changeset patch # User "Miroslav Lichvar <[EMAIL PROTECTED]>" # Date 1195647544 -3600 # Branch HEAD # Node ID 5d3c4cb859770cc3d57d37440f1a1b0d4d2e35ca # Parent 849daa6be9f56dc0e3505b9c7e9d18d1116a53cd Don't ignore $fro

Re: [Mutt] #2990: mutt-1.5.16: utf-8 support broken somewhere

#2990: mutt-1.5.16: utf-8 support broken somewhere between 1.5.13 and 1.5.16 Comment (by Sven Utcke): {{{ > > I didn't see anything in there which could be relevant. > > $assumed_charset might be. I didn't find any value for which there was no problem :-) > > What might be relevant tho

Re: [Mutt] #2981: header_cache: opening a changed Maildir takes way

#2981: header_cache: opening a changed Maildir takes way longer than it Changes (by madduck): * cc: [EMAIL PROTECTED] (added) Comment: Replying to [comment:1 pdmef]: > What's your value of $mail_check? 5 > What db backend do you use? None. This is all on an ext3/dircache filesystem.

Re: [Mutt] #2981: header_cache: opening a changed Maildir takes way

#2981: header_cache: opening a changed Maildir takes way longer than it Changes (by pdmef): * cc: [EMAIL PROTECTED] (added) Comment: I've now done some more tests with profiling. In the resulting gprof output, the only hot spot I see is from sorting the mailbox. As libc functions aren't cou

Re: wish: enable encrytion to arbitrary number of keys

Hi Thomas, * Thomas Roessler <[EMAIL PROTECTED]> [20. Nov. 2007]: > On 2007-11-20 17:21:11 +0100, Gregor Zattler wrote: > >> I second this or some other means to enable encryption to several >> keys which have no corresponding recipent in the email headers. > > I wonder if your use case is doing

Re: [Mutt] #2989: strsep not available on solaris

On Tue, Nov 20, 2007 at 04:19:31 -, Mutt wrote: > Commit 5307:033eba2d6834 broke Solaris build, as we don't have strsep > function. While looking around for alternative solution, I found this > reference: Wow, since when is mutt replacing missing Solaris functions? I found another one! ;-)

Re: [Mutt] #2958: mutt-1.5.16: mutt crash at start when enabling

#2958: mutt-1.5.16: mutt crash at start when enabling header caching in nsf directory with a (non-root) install Comment (by ): {{{ Hi all: I spent a large amount of time trying to get over the crashing bug, with no success. The same segfault appears in the latest 1.5.17. However, I d