2 new changesets in mutt:
http://dev.mutt.org/hg/mutt/rev/0ec4394636c4
changeset: 4967:0ec4394636c4
tag: tip
user:Michael Elkins <[EMAIL PROTECTED]>
date:Thu Mar 08 21:13:02 2007 -0800
summary: Add `UL' cast for Umask entry in MuttVars to supress compiler
warning.
h
Within a lists's items, we didn't include our text in a paragraph
properly.
To not let this happen again (hopefully), add a 'validate' target to
doc/Makefile which extracts the DTD url from the manual and tries to
validate against it using xmllint(1). This target has to be called
manually and is n
Hi,
when "parsing" numbers with atoi() and non-numeric input, the results
are usually unexpected. Currently, mutt uses atoi() in a number of
places. I've hacked up a patch adding mutt_atoi() (same for short and
long) as wrappers around strtol() to do the conversion (or test for it)
and report
This adds a 'validate' target to doc/Makefile which uses xmllint(1)
to validate manual.xml against the DTD given in the doctype (intended
for developers only).
Running it revealed two validation errors which this patch fixes:
1) We declare 'article' as the doctype but want to use 'book'
2) Within
The following reply was made to PR mutt/1503; it has been noted by GNATS.
From: Christoph Berg <[EMAIL PROTECTED]>
To: Mutt Bugs <[EMAIL PROTECTED]>
Cc:
Subject: Bug#328921: mutt/1503: problems with utf-8 terminals
Date: Fri, 9 Mar 2007 14:26:56 +0100
Hi,
mutt/1503 is still present in the cu
>Number: 2840
>Notify-List:
>Category: mutt
>Synopsis: "%>XY" in conditional clause (eg. "%?V?%>XY?") doesn't show Y
>Confidential: no
>Severity: minor
>Priority: low
>Responsible:mutt-dev
>State: open
>Keywords:
>Class: sw-bug
>Sub
Hello Takashi,
On Thursday, March 8, 2007 at 2:15:01 +0900, Takashi Takizawa wrote:
> The mutli-charset patch contains the followings:
> - wcwidth --> proposing
> http://www.emaillab.org/mutt/1.5.14/patch-1.5.14.tt.wcwidth.3
Thank you for the explanations. It appears the part of multi-chars
Synopsis: Cannot tag certain mail message using tag-all
State-Changed-From-To: open->closed
State-Changed-By: ab
State-Changed-When: Fri, 09 Mar 2007 15:47:49 +0100
State-Changed-Why:
Yet another duplicate of closed mistaken bug 2662. Use T.
to tag-all.
Comment added by ab on Fri, 09 Mar
On Friday, March 9 at 03:32 PM, quoth Alain Bench:
- pgp_charsethack (written by Tamotsu Takahashi)
http://www.emaillab.org/mutt/1.5.14/patch-1.5.14.tamo.pgp_charsethack.1
It also permits to send traditional inline PGP mails in any charset
of $send_charset (instead of forced $send_charset=
Synopsis: Mutt doesn't build with --without-wc-funcs
Comment added by vinc17 on Fri, 09 Mar 2007 17:21:10 +0100
On 2007-03-08 02:52:36 +0100, Alain Bench wrote:
> Hello Christoph!
>
> On Wednesday, March 7, 2007 at 13:36:05 +0100, Christoph Berg wrote:
>
> > 1. Filing bugs using the mail interface [...] Try to avoid MIME mail,
> > gnats will destroy it (any attachment, pgp signatures, etc.)
>
> Some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Kyle,
On Friday, March 9, 2007 at 8:08:43 -0700, Kyle Wheeler wrote:
> On Friday, March 9 at 03:32 PM, quoth Alain Bench:
>> [tamo.pgp_charsethack.1] also permits to send traditional inline PGP
>> mails in any charset of $send_charset (instea
On 2007-03-09 18:24:14 +0100, Alain Bench wrote:
> The whole thing is dead complex.
In fact it is dead simple. There is no character set tagging at
work, so all there is is a guess. Mutt takes its guess from the
OpenPGP spec (yeah, people don't really care), and from the native
character s
13 matches
Mail list logo
