configure: Don't treat --enable-ssl without POP or IMAP as an error

The current configure script treats --enable-ssl as an error when there's no POP or IMAP built in. That's not necessary, a warning will do. Changeset attached. -- Thomas Roessler <[EMAIL PROTECTED]> # HG changeset patch # User Thomas Roessler <[EMAIL PROTECTED]> # Date 1172827781 -3600 # Node

Re: mutt/1116: Fails to thread properly without an @ in msg ID

The following reply was made to PR mutt/1116; it has been noted by GNATS. From: Christoph Berg <[EMAIL PROTECTED]> To: Cameron Simpson <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: mutt/1116: Fails to thread properly without an @ in msg ID Date: Fri, 2 Mar 2007 12:48:25 +0100 Re: Camero

Re: mutt/1116: Fails to thread properly without an @ in msg ID

The following reply was made to PR mutt/1116; it has been noted by GNATS. From: Thomas Roessler <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Subject: Re: mutt/1116: Fails to thread properly without an @ in msg ID Date: Fri, 2 Mar 2007 12:59:23 +0100 Part of the problem is that there's little w

Re: configure: Don't treat --enable-ssl without POP or IMAP as an

Hi, * Thomas Roessler [07-03-02 10:34:34 +0100] wrote: The current configure script treats --enable-ssl as an error when there's no POP or IMAP built in. That's not necessary, a warning will do. Changeset attached. What about SMTP? bye, Rocco -- :wq!

Re: mutt/1116: Fails to thread properly without an @ in msg ID

Hi, * Thomas Roessler [07-03-02 13:05:02 +0100] wrote: Part of the problem is that there's little way to extract message-IDs from "In-Reply-To" headers -- except looking for valid syntax. Right, but what if the message-id is invalid? I think mutt should make up a set containing (uniquely) al

Re: Mutt 1.5.14 on Freebsd Display Problem

Hi, * Ryan Phillips [07-03-01 21:04:18 -0800] wrote: I narrowed down the problem with ncurses. I had WITH_MUTT_NCURSES=yes set in my /etc/make.conf file. Removing the line and letting mutt compile with the default slang library fixed the problem. Maybe somebody should file a bug report agai

Re: What's needed for mutt 1.6?

Hi, * Vincent Lefevre [07-02-28 22:42:37 +0100] wrote: On 2007-02-28 09:30:16 +, Rocco Rutte wrote: * Vincent Lefevre [07-02-28 03:43:34 +0100] wrote: >What are the output of "env | grep PATH", the include paths given by >"cpp -v", and the OS? $ env | grep PATH PATH=/sbin:/bin:/usr/sb

Re: What's needed for mutt 1.6?

Hi, * Christian Ebert [07-03-02 08:28:03 +0100] wrote: * Rocco Rutte on Wednesday, February 28, 2007 at 09:39:03 +: I played around with this. 2 questions/remarks: It seems to me that it breaks recog

Re: What's needed for mutt 1.6?

Hi, * Brendan Cully [07-02-28 14:13:53 -0800] wrote: We just need to make sure that eg asciidoc does what mutt needs. No more than that, I think. ACK. But first, I think we need a consensus what mutt actually needs. Even with asciidoc, for pretty single/chunked documents I think we'd have t

Re: mutt/1116: Fails to thread properly without an @ in msg ID

The following reply was made to PR mutt/1116; it has been noted by GNATS. From: Rocco Rutte <[EMAIL PROTECTED]> To: Mutt Developers Cc: [EMAIL PROTECTED] Subject: Re: mutt/1116: Fails to thread properly without an @ in msg ID Date: Fri, 2 Mar 2007 13:32:28 + Hi, * Thomas Roessler [07-03-

Re: Updating the manual

Hi, * Michael(tm) Smith [07-03-01 19:26:36 +0900] wrote: One reason why not would be to make sure that asciidoc could actually provide the same level of semantic markup to capture the semantics of the current manual marked up in DocBook, and to do it in a way that does not end up making the sou

Re: What's needed for mutt 1.6?

On Wed, Feb 28, 2007 at 02:13:53PM -0800, Brendan Cully wrote: > We just need to make sure that eg asciidoc does what mutt needs. No > more than that, I think. The problem is that what mutt needs will expand over time. Isn't that why the doc generation was moved to docbook in the first place...?

Re: Mutt 1.5.14 on Freebsd Display Problem

On Friday, March 2 at 01:45 PM, quoth Rocco Rutte: I narrowed down the problem with ncurses. I had WITH_MUTT_NCURSES=yes set in my /etc/make.conf file. Removing the line and letting mutt compile with the default slang library fixed the problem. Maybe somebody should file a bug report again

Re: What's needed for mutt 1.6?

On Friday, 02 March 2007 at 14:47, Paul Walker wrote: > On Wed, Feb 28, 2007 at 02:13:53PM -0800, Brendan Cully wrote: > > > We just need to make sure that eg asciidoc does what mutt needs. No > > more than that, I think. > > The problem is that what mutt needs will expand over time. Isn't that w

Re: Mutt 1.5.14 on Freebsd Display Problem

On Thu, Mar 01, 2007 at 21:04:18 -0800, Ryan Phillips wrote: > Paul Walker <[EMAIL PROTECTED]> said: >> On Thu, Mar 01, 2007 at 01:23:28PM -0800, Ryan Phillips wrote: >> > >> This problem didn't happen with 1.5.13. If it makes a difference I'm > >> using putty to ssh into the box. >> >> I seem t

Re: What's needed for mutt 1.6? (send multipart/alternative)

=- Jim Allen wrote on Wed 28.Feb'07 at 20:02:57 -0600 -= > A useful feature would be providing the equivalent of the > mime_forward configuration variable but which applies to replies > (i.e.mime_reply which allows reply with attachments). This > allows one to preserve the original note and its fo

Re: What's needed for mutt 1.6? (send multipart/alternative)

On 2007-03-02 19:10:25 +0100, Rado S wrote: > Let them have their way, why do _you_ (or mutt) have to (be able > to) send HTML? Tables. There are actually valid reasons to send HTML stuff. -- Thomas Roessler <[EMAIL PROTECTED]>

Re: What's needed for mutt 1.6?

Hi, * Christian Ebert [07-03-02 08:28:03 +0100] wrote: It seems to me that it breaks recognition of correct sig dashes in the pager (or is it something in my setup?). Thanks to your help this is fixed in:

Re: What's needed for mutt 1.6? (send multipart/alternative)

=- Thomas Roessler wrote on Fri 2.Mar'07 at 19:12:08 +0100 -= > > Let them have their way, why do _you_ (or mutt) have to (be > > able to) send HTML? > > Tables. > > There are actually valid reasons to send HTML stuff. Sure, but why can't this be a regular attachment multipart/mixed, why does

Re: What's needed for mutt 1.6?

On Fri, Mar 02, 2007 at 02:10:00PM +, Rocco Rutte wrote: > Brendan and me already discussed some the idea of adding $wrap on IRC > which specifies the width of text, and that it could default to > columns-$wrapmargin (in the implementation, not config). > i'd make $wrap take positive numbers

What MuttPeople are doing

Moin, let's keep track of who does what so we know who to address in times of need (when something fails, needs a change or is missing). Please add _yourself_ to MuttPeople on the wiki. Especially of interest are distro contacts. If you know one who isn't subscribed himself here, please ask wheth

Re: What's needed for mutt 1.6?

* Rocco Rutte on Friday, March 02, 2007 at 18:16:51 +: > * Christian Ebert [07-03-02 08:28:03 +0100] wrote: >> It seems to me that it breaks recognition of correct sig dashes >> in the pager (or is it something in my setup?). > Thanks to your help this is fixed in: > >

flow & wrap (was: What's needed for mutt 1.6?)

* Rocco Rutte on Friday, March 02, 2007 at 14:10:00 +: > * Christian Ebert [07-03-02 08:28:03 +0100] wrote: >> * Rocco Rutte on Wednesday, February 28, 2007 at 09:39:03 +: [...] > Hmm. I never had pr

Re: Mutt 1.5.14 on Freebsd Display Problem

Udo Schweigert <[EMAIL PROTECTED]> said: > On Thu, Mar 01, 2007 at 21:04:18 -0800, Ryan Phillips wrote: > > Paul Walker <[EMAIL PROTECTED]> said: > >> On Thu, Mar 01, 2007 at 01:23:28PM -0800, Ryan Phillips wrote: > >> > > >> This problem didn't happen with 1.5.13. If it makes a difference I'm >

Re: Updating the manual

On 2007-03-02 14:43:18 +, Rocco Rutte wrote: > Well, the manual now makes use of only very few DocBook tags. But the > problem to me seems that neither DocBook nor asciidoc contain those we > need like one for referencing variables (including layout, > cross-reference, auto-indexing, etc). T

Re: What's needed for mutt 1.6?

On 2007-03-02 13:59:40 +, Rocco Rutte wrote: > I have this in config.h: > > configure:8252: checking for waddnwstr in -lncurses > configure:8282: gcc -o conftest -g -O2 -I/usr/local/include > -L/usr/local/lib conftest.c -lncurses >&5 The -I and -L seem to be a bug in the configure s

Re: mutt/1116: Fails to thread properly without an @ in msg ID

The following reply was made to PR mutt/1116; it has been noted by GNATS. From: Cameron Simpson <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: mutt/1116: Fails to thread properly without an @ in msg ID Date: Sat, 3 Mar 2007 11:45:50 +1100 On 02Mar2007 13:05, Thomas

Re: What's needed for mutt 1.6? (send multipart/alternative)

On Mar 2, 2007, at 12:10 PM, Rado S wrote: =- Jim Allen wrote on Wed 28.Feb'07 at 20:02:57 -0600 -= A useful feature would be providing the equivalent of the mime_forward configuration variable but which applies to replies (i.e.mime_reply which allows reply with attachments). This allows one

Re: What's needed for mutt 1.6? (xterm title)

On Monday, 26 February 2007 at 18:37, Christoph Berg wrote: > Re: Brendan Cully 2007-02-24 <[EMAIL PROTECTED]> > > > Small remark: it seems to have a hardwired set of "good" > > > terminals. Neither or mine (rxvt-unicode and screen-256color-bce) > > > is one it. Or is that just for the default sett

Re: What's needed for mutt 1.6? (xterm title)

On Friday, 02 March 2007 at 18:35, Brendan Cully wrote: > I had a look around, and David Champion's fmtpipe patch almost does > this. Unfortunately it seems to break down in the presence of %? > conditionals. If that could be fixed, it seems like a workable > solution with other potentially cool us

[PATCH] Add $status_hook for xterm title updates

# HG changeset patch # User Brendan Cully <[EMAIL PROTECTED]> # Date 1172895865 28800 # Node ID c36482e98b8130395c5697c21d060690b57d58e4 # Parent 256c86830a368e944b0305258e20b670eb0aea75 Add $status_hook for xterm title updates. If $status_hook is set, the command it points to will be called and

[PATCH] Add $umask for mailboxes and attachments

# HG changeset patch # User Brendan Cully <[EMAIL PROTECTED]> # Date 1172898753 28800 # Node ID d61d41715015d975d5643a41cd8dc36b8a7dc97b # Parent c36482e98b8130395c5697c21d060690b57d58e4 Add $umask for mailboxes and attachments diff -r c36482e98b81 -r d61d41715015 attach.c --- a/attach.c Fri Mar

mutt: 4 new changesets

4 new changesets in mutt: http://dev.mutt.org/hg/mutt/rev/472e100053ed changeset: 4944:472e100053ed branch: HEAD tag: tip user:Brendan Cully <[EMAIL PROTECTED]> date:Fri Mar 02 21:17:19 2007 -0800 summary: Ignore more built files http://dev.mutt.org/hg/mutt/rev/