headers
Brendan Cully | 1 Sep 09:00
Gravatar

mutt: 11 new changesets

11 new changesets in mutt:

http://dev.mutt.org/hg/mutt/rev/b6d07a662c7f
changeset:   5525:b6d07a662c7f
branch:      HEAD
tag:         tip
user:        Rocco Rutte <pdmef <at> gmx.net>
date:        Sun Aug 31 23:36:36 2008 +0200
summary:     Fix pager to respect $wrap_search

http://dev.mutt.org/hg/mutt/rev/f4b10e6b415c
changeset:   5524:f4b10e6b415c
branch:      HEAD
user:        Rocco Rutte <pdmef <at> gmx.net>
date:        Sun Aug 31 23:28:54 2008 +0200
summary:     Backout [e5610347fb3f] for further discussion

http://dev.mutt.org/hg/mutt/rev/581037c15012
changeset:   5523:581037c15012
branch:      HEAD
user:        Rocco Rutte <pdmef <at> gmx.net>
date:        Sun Aug 31 21:13:06 2008 +0200
summary:     Manual: Fix trailing \ for $preconnect

http://dev.mutt.org/hg/mutt/rev/6d80c3d5b7aa
changeset:   5522:6d80c3d5b7aa
branch:      HEAD
user:        Rocco Rutte <pdmef <at> gmx.net>
date:        Sun Aug 31 21:12:19 2008 +0200
summary:     makedoc: Fix fall-through in [c11ce7feaa3e]
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Sep 14:28

Re: [Mutt] #3112: tokyocabinet as hcache database

#3112: tokyocabinet as hcache database
---------------------------+------------------------------------------------
  Reporter:  blacktrash    |       Owner:  mutt-dev
      Type:  enhancement   |      Status:  new     
  Priority:  minor         |   Milestone:          
 Component:  header cache  |     Version:  1.5.18  
Resolution:                |    Keywords:  patch   
---------------------------+------------------------------------------------
Changes (by pdmef):

  * keywords:  => patch

Comment:

 Add tokyocabinet patch by exg, source: http://tomaw.net/~exg/mutt/mutt-
 tokyocabinet.diff.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3112#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Mutt | 1 Sep 22:55

Re: [Mutt] #3112: tokyocabinet as hcache database

#3112: tokyocabinet as hcache database
---------------------------+------------------------------------------------
  Reporter:  blacktrash    |       Owner:  mutt-dev
      Type:  enhancement   |      Status:  new     
  Priority:  minor         |   Milestone:          
 Component:  header cache  |     Version:  1.5.18  
Resolution:                |    Keywords:  patch   
---------------------------+------------------------------------------------

Comment(by blacktrash):

 works like a charm! very nice. thank you!

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3112#comment:2>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Brendan Cully | 2 Sep 09:00
Gravatar

mutt: new changeset

New changeset in mutt:

http://dev.mutt.org/hg/mutt/rev/17adea9cdff6
changeset:   5526:17adea9cdff6
branch:      HEAD
tag:         tip
user:        Rocco Rutte <pdmef <at> gmx.net>
date:        Mon Sep 01 18:23:35 2008 +0200
summary:     Add note about locale-safe hcaches to UPDATING as it's a user-visible change

--

-- 
Repository URL: http://dev.mutt.org/hg/mutt
Permalink | Reply | 0 comments |
headers
Mutt | 2 Sep 11:15

Re: [Mutt] #3001: format=flowed (interoperability) (was:

#3001: format=flowed (interoperability)
--------------------------+-------------------------------------------------
  Reporter:  js           |       Owner:  pdmef              
      Type:  enhancement  |      Status:  new                
  Priority:  minor        |   Milestone:  1.6                
 Component:  mutt         |     Version:                     
Resolution:               |    Keywords:  format=flowed patch
--------------------------+-------------------------------------------------

Comment(by pdmef):

 Update/summary to make deciding easier.

 Issue 1 is interoperability. The ff.diff patch adds $flowed_compat. The
 changes are:

   * when making format=flowed  replies to format=fixed messages, trailing
 spaces are trimmed: this is to make sure that when you make an f=f reply
 you suddenly don't produce flowable paragraphs because the format=fixed
 original mail had some trailing spaces.
   * when making format=fixed replies to format=flowed messages,
 $indent_string should be used since it's still a format=fixed message. And
 as you may then quote flowed paragraphs with a possibly non-f=f compatible
 $indent_string (as is the default), it wouldn't be valid f=f anymore if
 somebody made an f=f reply on your message again; as a result, we also
 trim spaces when making a fixed reply to a flowed message.

 Issue 2 is an objection by TLR about the new f=f handler. Quote in
 20080118120119.GA28830 <at> iCoaster.does-not-exist.org:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 2 Sep 20:36

Re: [Mutt] #3000: Deleting >50k messages from IMAP boxes fails with

#3000: Deleting >50k messages from IMAP boxes fails with Fatal error:
---------------------+------------------------------------------------------
  Reporter:  myon    |       Owner:  brendan 
      Type:  defect  |      Status:  reopened
  Priority:  minor   |   Milestone:  1.6     
 Component:  IMAP    |     Version:  1.5.17  
Resolution:          |    Keywords:          
---------------------+------------------------------------------------------

Old description:

> {{{
> Hi,
>
> I'm trying to delete some 200k messages from a 240k IMAP folder.
> Tagging ~m1-10000 and deleting/expunging works. For larger selections
> (I first tried 200k and then 50k), mutt fails with
>
> Fatal error: word too long
>
> and closes the folder.
>
> Mutt version 1.5.17, both tarball and hg HEAD.
>
> Christoph
> }}}

New description:

 {{{
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kyle Wheeler | 3 Sep 19:47

Timeouts?

Has anyone else noticed a change in pager-based timeouts?

I generally track mutt's mercurial tree, and I noticed that recently 
mutt started timing out (being "Disconnected for Inactivity") if I let 
it sit while viewing a message (i.e. in the internal pager). However, 
I can let it sit on a mailbox index display forever without trouble.

Any idea what might be causing the problem?

I'm assuming some change in either [12a6de725483] or [4f67fc336986], 
but I haven't figured out what exactly did it yet.

~Kyle
--

-- 
No man needs a vacation so much as the man who has just had one.
                                                      -- Elbert Hubbard
Permalink | Reply | 12 comments |
headers
Brendan Cully | 3 Sep 20:12
Gravatar

Re: Timeouts?

On Wednesday, 03 September 2008 at 12:47, Kyle Wheeler wrote:
> Has anyone else noticed a change in pager-based timeouts?
>
> I generally track mutt's mercurial tree, and I noticed that recently mutt 
> started timing out (being "Disconnected for Inactivity") if I let it sit 
> while viewing a message (i.e. in the internal pager). However, I can let 
> it sit on a mailbox index display forever without trouble.
>
> Any idea what might be causing the problem?

hmm, it was supposed to have gotten better, not worse :)

> I'm assuming some change in either [12a6de725483] or [4f67fc336986], but I 
> haven't figured out what exactly did it yet.

It'd be great if you could bisect.
Permalink | Reply | 11 comments |
headers
Rocco Rutte | 3 Sep 21:31
Picon

Manual toc depth

Hi,

I'd like to commit a change which makes the manual contain only chapters
and sections in the manual to trim the table of contents, mainly to
remove hundreds of sections for config options.

Due to Brendan recalling objections I'd like to know what these are.

The change (already backed out) would be identical to
http://dev.mutt.org/hg/mutt/rev/e5610347fb3f.

Are there any objections?

Regards, Rocco
Permalink | Reply | 7 comments |
headers
Kyle Wheeler | 3 Sep 22:44

Re: Manual toc depth

On Wednesday, September  3 at 09:31 PM, quoth Rocco Rutte:
> I'd like to commit a change which makes the manual contain only 
> chapters and sections in the manual to trim the table of contents, 
> mainly to remove hundreds of sections for config options.
>
> Due to Brendan recalling objections I'd like to know what these are.
>
> The change (already backed out) would be identical to 
> http://dev.mutt.org/hg/mutt/rev/e5610347fb3f.
>
> Are there any objections?

I don't recall objecting before, but it seems to me that this is 
solving the wrong problem. The real problem is that the config options 
shouldn't each have their own section. There are several level-2 
sections (such as "editing-intro", "simple-patterns", and similar) 
that probably *ought* to be in the table of contents. I realize it 
would be a lot more work, but shouldn't the config options be more 
appropriately reformatted so they don't define their own sections?

If I understand it correctly, in the XML, <sect2 id="abort-nosubject"> 
is equivalent to \subsection{abort-nosubject} in LaTeX. The "right" 
solution would be to describe config options using a more appropriate 
semantic construct that correctly signifies the organizational 
importance of the config options (such as putting them in an itemized 
list or something similar) rather than simply asserting that sect2's 
are no longer sufficiently important to be in the ToC. Isn't the real 
problem that config options shouldn't define level-2 manual sections, 
rather than that level-2 manual sections shouldn't be in the ToC?
(Continue reading)

Permalink | Reply | 6 comments |

Gmane