Re: changeset: 4828ffd619f6 causes bus error

On Saturday, 31 March 2007 at 08:49, Christian Ebert wrote: > Hello, > > changeset: 5029:4828ffd619f6 > user:Brendan Cully <[EMAIL PROTECTED]> > date:Fri Mar 30 19:51:44 2007 -0700 > files: mh.c mutt.h > description: > Move mtime_cur from CONTEXT to mh_data > > > This one

mutt: 7 new changesets

7 new changesets in mutt: http://dev.mutt.org/hg/mutt/rev/d5ab883ef90a changeset: 5031:d5ab883ef90a tag: tip user:Daniel Burrows <[EMAIL PROTECTED]> date:Fri Mar 30 21:26:16 2007 -0700 summary: Fix handling of DB4 hcache open failure. (closes: #2714) http://dev.mutt.

changeset: 4828ffd619f6 causes bus error

Hello, changeset: 5029:4828ffd619f6 user:Brendan Cully <[EMAIL PROTECTED]> date:Fri Mar 30 19:51:44 2007 -0700 files: mh.c mutt.h description: Move mtime_cur from CONTEXT to mh_data This one lets Mutt die on launch with bus error here. Configuration: ./prepare --prefix=

Re: [Mutt] #2676: mutt + imap header results in a NULL pointer

#2676: mutt + imap header results in a NULL pointer dereference crash Old description: > {{{ > Whenever I try to check my employer's mail (via IMAP+TLS), > I use IMAP header-caching. However, mutt crashes on this particular > mailbox. gdb(1) gives: > > Fetching message headers... [402/402] > Prog

Re: [Mutt] #2203: Mutt freezes regularily when fetching new messages

#2203: Mutt freezes regularily when fetching new messages Changes (by brendan): * status: new => closed * resolution: => worksforme Old description: > {{{ > Hi, > > i use mutt as my MUA at work. It connects with a mail server via IMAP, > but sometimes, when fetching a new message, mutt fr

Re: [Mutt] #2133: flea uses wrong email / [EMAIL PROTECTED] broken

#2133: flea uses wrong email / [EMAIL PROTECTED] broken Changes (by brendan): * status: new => closed * resolution: => wontfix Old description: > {{{ > flea can't send bug^H^H^Hflea-reports: > >- The following addresses had permanent fatal errors - > <[EMAIL PROTECTED]> >

Re: [Mutt] #2151: core dump upon fetching message headers with

#2151: core dump upon fetching message headers with header cache enabled Changes (by brendan): * priority: minor => major * status: reopened => closed * resolution: => worksforme Old description: > {{{ > "Fetching message headers... [91700/91916]Segmentation fault (core > dumped)" has

Re: [Mutt] #2184: SEGV in mutt_match_rx_list()

#2184: SEGV in mutt_match_rx_list() Old description: > {{{ > Since I rebuilt mutt from a recent CVS checkout, I observe sporadic > crashes. Today I managed to create a core: > > > Core was generated by `mutt'. > Program terminated with signal 11, Segmentation fault. > > warning: current_sos: Can

Re: [Mutt] #2199: [gpgme] Sending ^C while running pinentry

#2199: [gpgme] Sending ^C while running pinentry segfaults Mutt Old description: > When entering your passphrase into the pinentry application when using > Mutt in combination with GPGME, it's possible to segfault Mutt. Just > press ^C in the terminal running Mutt (or pinentry, when using the cur

Re: [Mutt] #2199: [gpgme] Sending ^C while running pinentry

#2199: [gpgme] Sending ^C while running pinentry segfaults Mutt Changes (by brendan): * priority: minor => major * component: mutt => crypto Old description: > {{{ > When entering your passphrase into the pinentry application when using > Mutt in combination with GPGME, it's possible to s

Re: [Mutt] #2747: imap_keepalive ignored when less than timeout and

#2747: imap_keepalive ignored when less than timeout and too much idle Changes (by brendan): * owner: mutt-dev => brendan * priority: critical => minor * milestone: => 1.6 Old description: > {{{ > When you set "imap_keepalive" < IMAP-server-timeout < "timeout", > then IMAP-server will

Re: [Mutt] #2441: Segmentation fault in batch mode with large files

#2441: Segmentation fault in batch mode with large files Changes (by brendan): * priority: critical => major * status: reopened => closed * resolution: => fixed Old description: > {{{ > Sending a large file via command line causes a segmentation fault > > There was one important piece

Re: [Mutt] #714: Lines starting From aren't escaped saving from

#714: Lines starting From aren't escaped saving from Maildir to mbox Changes (by brendan): * priority: critical => major Old description: > {{{ > Package: mutt > Version: 1.2.5i > Severity: normal > > -- Please type your report below this line > > Send a mail to an address which is saved int

Re: [Mutt] #2033: buffer overflow in attachment decoding function

#2033: buffer overflow in attachment decoding function Changes (by brendan): * priority: critical => major Old description: > {{{ > There is a potentially serious buffer overflow in > mutt-1.4.2/handler.c:mutt_decode_xbit() as well as the uuencode and other > attachment decoding functions, d

Re: [Mutt] #2714: Segfaults when trying to read header cache if cwd

#2714: Segfaults when trying to read header cache if cwd does not exist. Changes (by brendan): * status: new => closed * resolution: => fixed Old description: > {{{ > > Hi, > > the attached patch looks sane to me. > > Christoph > > Reply-To: Daniel Burrows <[EMAIL PROTECTED]>, [EMAIL PROT

Re: [Mutt] #2274: mutt crashes on startup

#2274: mutt crashes on startup Changes (by brendan): * status: new => closed * resolution: => worksforme Old description: > {{{ > mutt crashes on every startup. > >How-To-Repeat: > - untar from source > - correct keymap.c/.h (one line in each file) for gcc 4.x > - configure > - make > and

Re: [Mutt] #2444: segfault when trying to list folders

#2444: segfault when trying to list folders Changes (by brendan): * status: assigned => closed * resolution: => fixed Old description: > {{{ > Doing change-folder+ (c+?) (to list folders) causes my mutt > to segfault. > > --- > > Here's the part of the debug log before the segfault. > > T

Re: [Mutt] #2772: Patch imap_recent option to use RECENT instead of

#2772: Patch imap_recent option to use RECENT instead of UNSEEN Changes (by brendan): * status: assigned => closed * resolution: => fixed Comment: I think I have a somewhat more general fix in [0cb476dc70a7] and [dc7ed7df43aa]. -- Ticket URL:

[Mutt] #2871: Undelivered Mail Returned to Sender

#2871: Undelivered Mail Returned to Sender {{{ This is the mail system at host peyresourde.cs.ubc.ca. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do

Re: [Mutt] #1467: checking of imap mailbox delays opening inbox

#1467: checking of imap mailbox delays opening inbox Old description: > {{{ > Package: mutt > Version: mutt-1.5.3i-0 > Severity: normal > > -- Please type your report below this line > > if you have an imap folder watched via "mailboxes" it will also be > checked > for new mail right at the start

Re: dates on trac

On Saturday, 31 March 2007 at 04:27, Vincent Lefevre wrote: > Web pages on trac use ambiguous dates, such as 06/01/02. Could the > configuration be changed to use ISO-8601 dates, please? Done. pgpIkE4aSEZw2.pgp Description: PGP signature

Re: [PATCH] Add $umask for mailboxes and attachments

On Wednesday, 21 March 2007 at 10:19, Brendan Cully wrote: > So how about the following strategy for $umask: > > 1. I back out my patch > > 2. we save the existing $umask when setting it to 077 in main > 3. we temporarily restore that umask for saving attachments and pipe >commands > 4. we cr

dates on trac

Web pages on trac use ambiguous dates, such as 06/01/02. Could the configuration be changed to use ISO-8601 dates, please? -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arith

built-in SMTP support

On Friday, 30 March 2007 at 18:43, Charles Killian wrote: > Is there a way to set it to use TLS in the applied patch? I found some > reference on http://www.deez.info/sengelha/code/mutt-libesmtp/ to > smtp_require_tls, but when I set it, mutt warns of an unrecognized > variable. $ssl_starttls sho

Re: What's needed for mutt 1.6?

Is there a way to set it to use TLS in the applied patch? I found some reference on http://www.deez.info/sengelha/code/mutt-libesmtp/ to smtp_require_tls, but when I set it, mutt warns of an unrecognized variable. Thanks - Chip On Fri, Feb 23, 2007 at 10:42:10PM -0800, Brendan Cully wrote: > On

Re: [Mutt] #2790: re-executing a "too long" 'color body ...' cmd

#2790: re-executing a "too long" 'color body ...' cmd causes segv crash after a while Changes (by brendan): * priority: critical => major Old description: > {{{ > When a "color body ..." cmd, which fails because it's too long > (color.c:518), > is executed several times, crashes mutt eventua

[Mutt] #2870: Re: mutt/2870: color index foo foo ~h pattern causes many fileops

#2870: Re: mutt/2870: color index foo foo ~h pattern causes many fileops {{{ On 2007-03-30 04:25:04 +0200, Michael Elkins wrote: > Unfortunately, it is possible that a message in the cur/ subdirectory is > modified in another Mutt which would be undetectable without a full > rescan. Oper

Re: What's needed for mutt 1.6?

On Friday, 30 March 2007 at 00:24, Brendan Cully wrote: > On Friday, 23 February 2007 at 13:40, Jorgen Hermanrud Fjeld wrote: > > Hello! > > > > On 2007-02-22 09:30:33, Brendan Cully wrote: > > > So, I'd like to hear once again which patches everyone would > > > like to see in 1.6 (and which patch

Re: mutt cache sensitivity

Hi, * Kyle Wheeler [07-03-29 08:41:06 -0600] wrote: On Thursday, March 29 at 02:34 PM, quoth Rocco Rutte: Second, these problems are more or less solved. The header cache does checksum validation on its own, so we only need to bump an internal id field upon each incompatible layout change. Mu

Re: mutt/2790: re-executing a "too long" 'color body ...' cmd causes segv crash after a while

Synopsis: re-executing a "too long" 'color body ...' cmd causes segv crash after a while Comment added by rado on Fri, 30 Mar 2007 15:40:11 +0200 Clarify How-To-Repeat.

Re: What's needed for mutt 1.6? (easy switching between local and

=- Brendan Cully wrote on Thu 29.Mar'07 at 18:53:25 -0700 -= > > >> Yup, these are just too many keypresses if you're not using > > >> that folder=... stuff. > > > > > > I still can't quite figure out if you're reporting this as a > > > bug or not. :) If you are, then how would you propose > > >

Re: mutt/2538: "make -j2 dist" does not work (bad dependency?)

Synopsis: "make -j2 dist" does not work (bad dependency?) State-Changed-From-To: closed->open State-Changed-By: pdmef State-Changed-When: Fri, 30 Mar 2007 11:42:29 +0200 State-Changed-Why: Reopened as it's not fixed. If it works then only by accident since makedoc is still compiled twice, i.e. t