Re: [Mutt] #3040: charset difference between index browser and pager

#3040: charset difference between index browser and pager Comment (by Miek Gieben): {{{ [19 Mar, @00:49 CET, Mutt wrote in "Re: [Mutt] #3040: charset diff ..."] > #3040: charset difference between index browser and pager > > > So I would still consider this a bug in mutt... > > There is

Re: [Mutt] #3040: charset difference between index browser and pager

#3040: charset difference between index browser and pager Comment (by brendan): Are you using gmail IMAP by any chance? The gmail IMAP server has a bug which produces these symptoms in mutt. See #2997 for more info. -- Ticket URL:

Re: [Mutt] #3041: imap fetch segfault

#3041: imap fetch segfault Changes (by brendan): * owner: mutt-dev => brendan * component: mutt => IMAP * milestone: => 1.6 Old description: > Hello, > > I am getting random segment fault during imap fetching from the outlook > server. > > I take a look at the the core dump. > > Progra

Re: [Mutt] #3041: imap fetch segfault

#3041: imap fetch segfault Comment (by brendan): 558 if (h && h->active && h->index+1 == msgno) Hmm, h must be neither NULL nor a valid header. That is certainly troubling. Usually the header array is preallocated and zeroed before headers are fetched into it, but there may be some

Re: [Mutt] #3040: charset difference between index browser and pager

#3040: charset difference between index browser and pager Comment (by Miek Gieben): {{{ [19 Mar, @16:53 CET, Mutt wrote in "Re: [Mutt] #3040: charset diff ..."] > #3040: charset difference between index browser and pager > > Comment (by brendan): > > Are you using gmail IMAP by any chance

wildcard in doc/Makefile.{am,in} causes problems when hacking OPS files

Hi, I have recently been working on some enhancements for Mutt which include a change to the file OPS. I like to keep copies of the original versions of the files I change and use the .orig suffix to indicate such. My editor also keeps backups of files changed and it uses the suffix ~. This me

Re: wildcard in doc/Makefile.{am,in} causes problems when hacking

On Wednesday, March 19 at 09:05 PM, quoth N.J. Mann: --- doc/Makefile.am.orig2007-11-30 08:00:04.0 + +++ doc/Makefile.am @@ -43,6 +43,9 @@ ChangeLog.old \ README NEWS TODO README.SECURITY README.SSL +OPS = $(top_srcdir)/OPS $(top_s

Default groups

While figuring out a way to colour e-mails from people in my aliases, I've discovered mutt's address groups. That will do what I'm after, except that it looks like I have to add a -group option to all my alias definitions to make it work. That will break whenever I use the 'a' command to add a new

Re: wildcard in doc/Makefile.{am,in} causes problems when hacking

In message <[EMAIL PROTECTED]>, Kyle Wheeler ([EMAIL PROTECTED]) wrote: > On Wednesday, March 19 at 09:05 PM, quoth N.J. Mann: >> --- doc/Makefile.am.orig 2007-11-30 08:00:04.0 + >> +++ doc/Makefile.am >> @@ -43,6 +43,9 @@ >> ChangeLog.old

Re: wildcard in doc/Makefile.{am,in} causes problems when hacking

On Wednesday, March 19 at 09:54 PM, quoth N.J. Mann: NO. Do *NOT* edit auto-generated files (such as Makefile.in -- automake Hey! I _did_ say automake was something I didn't know much about! Where's your solution? Sorry, I didn't mean to come off as insulting, I just wanted to be very clea