Re: [Mutt] #3278: info/error message stripped 2 columns before the

2009-06-22 Thread Mutt
#3278: info/error message stripped 2 columns before the right of the terminal in command line --+- Reporter: vinc17 | Owner: mutt-dev Type: defect | Status: closed Priority: minor| Mileston

Re: [Mutt] #3277: smime_keys uses obsolete perl module

2009-06-22 Thread Mutt
#3277: smime_keys uses obsolete perl module --+- Reporter: raorn| Owner: mutt-dev Type: enhancement | Status: closed Priority: trivial | Milestone: Component: mutt

Re: [Mutt] #3276: iswupper() replacement gets it backward

2009-06-22 Thread Mutt
#3276: iswupper() replacement gets it backward ---+ Reporter: dhduvall | Owner: mutt-dev Type: defect| Status: closed Priority: major | Milestone: Component: charset | Ve

Re: [Mutt] #3278: info/error message stripped 2 columns before the

2009-06-22 Thread Mutt
#3278: info/error message stripped 2 columns before the right of the terminal in command line --+- Reporter: vinc17 | Owner: mutt-dev Type: defect | Status: closed Priority: minor| Mileston

Re: atime/mtime (Was: mutt: 5 new changesets)

2009-06-22 Thread Kyle Wheeler
On Monday, June 22 at 10:43 AM, quoth Derek Martin: On Mon, Jun 22, 2009 at 04:43:27PM +0200, Moritz Barsnick wrote: I think this behavior is not desired. I meant to add that if you want to mark something that needs your attention, but *don't* want to treat it as new (unseen) mail, then you sh

Re: atime/mtime (Was: mutt: 5 new changesets)

2009-06-22 Thread Derek Martin
On Mon, Jun 22, 2009 at 04:43:27PM +0200, Moritz Barsnick wrote: > I think this behavior is not desired. I meant to add that if you want to mark something that needs your attention, but *don't* want to treat it as new (unseen) mail, then you should not leave it marked new; you should instead flag

Re: atime/mtime (Was: mutt: 5 new changesets)

2009-06-22 Thread Derek Martin
On Mon, Jun 22, 2009 at 04:43:27PM +0200, Moritz Barsnick wrote: > I applied these two on top of 1.5.20. But I think changeset > 5922:9ae13dedb5ed doesn't make sense to me. If I leave any mail marked > as new (which I do if I intend to yet read it or work on it) in any > folder, mutt marks the who

atime/mtime (Was: mutt: 5 new changesets)

2009-06-22 Thread Moritz Barsnick
On Sat, Jun 20, 2009 at 00:00:03 -0700, Brendan Cully wrote: > http://dev.mutt.org/hg/mutt/rev/9ae13dedb5ed > changeset: 5922:9ae13dedb5ed > branch: HEAD > tag: tip > user:Rocco Rutte > date:Fri Jun 19 22:49:54 2009 +0200 > summary: Fixup atime for mbox/mmdf also

Re: fadvise WILLNEED for tokyocabinet header cache

2009-06-22 Thread Andrea Arcangeli
On Sun, Jun 21, 2009 at 11:05:28PM +0200, Rocco Rutte wrote: > I think making it faster is always good. However, there're some more eheh me too ;) > points that would have to be solved to get the patch ready for > inclusion. For example test if posix_fadvise() is available, why only That requ

[Mutt] #3278: info/error message stripped 2 columns before the right of the terminal in command line

2009-06-22 Thread Mutt
#3278: info/error message stripped 2 columns before the right of the terminal in command line -+-- Reporter: vinc17 | Owner: mutt-dev Type: defect | Status: new Priority: minor| Milestone:

Re: changeset 5920 / manual.xml.head

2009-06-22 Thread Vincent Lefevre
Hi, On 2009-06-20 15:26:49 +0200, Rocco Rutte wrote: > I've tried to clarified the issue and extended it a bit because the > conversion rule (type1 <-> string <-> type2) applies to all commands. Thanks. This is much better... except In case of parsing errors, mutt will print error messages as

mutt: 4 new changesets

2009-06-22 Thread Brendan Cully
4 new changesets in mutt: http://dev.mutt.org/hg/mutt/rev/ed7eb5de7536 changeset: 5930:ed7eb5de7536 branch: HEAD tag: tip user:Rocco Rutte date:Sun Jun 21 21:57:28 2009 +0200 summary: Pass buffer size to mutt_mktemp() http://dev.mutt.org/hg/mutt/rev/7f0f11b1b6f