Mutt | 20 May 2013 17:15

[Mutt] #3643: Man pages for pgpewrap and pgpring and other doc fixes

#3643: Man pages for pgpewrap and pgpring and other doc fixes
---------------------+----------------------
 Reporter:  hhorak   |      Owner:  mutt-dev
     Type:  defect   |     Status:  new
 Priority:  trivial  |  Milestone:
Component:  doc      |    Version:
 Keywords:           |
---------------------+----------------------
 Hi, this is only unimportant patch, that adds some missing options in doc
 and adds man pages for binaries pgpewrap and pgpring.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3643>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Mutt | 3 May 2013 20:41

[Mutt] #3642: Missing header when building against S-Lang

#3642: Missing header when building against S-Lang
-------------------------+---------------------
 Reporter:  baskerville  |      Owner:  brendan
     Type:  defect       |     Status:  new
 Priority:  major        |  Milestone:
Component:  IMAP         |    Version:
 Keywords:               |
-------------------------+---------------------
 The following:

 {{{
 ./prepare \
     --prefix=/usr \
     --sysconfdir=/etc \
     --enable-gpgme \
     --enable-hcache \
     --with-slang=/usr \
     --with-regex \
     --with-idn
 make
 }}}

 yields

 {{{
 crypt-gpgme.c: In function ‘init_common’:
 crypt-gpgme.c:4369:15: error: ‘true’ undeclared (first use in this
 function)
      has_run = true;
 }}}
(Continue reading)

Kevin J. McCarthy | 28 Apr 2013 00:48
Picon
Gravatar

[PATCH 0 of 3] Ticket #3082 preserve current input in history when cycling

I'm attaching a 3-part patch that is one possible solution to this. It
creates an extra slot in the History ring for a scratch buffer (at
h->last). If you are editing inside that buffer, it is preserved when
you scroll up/down through the history. Editing while in other places in
history are *not* preserved with this patch.

I thought about creating a scratch history array instead, and trying to
preserve all edits in a temporary history array until done. But that
seemed a lot more complexity and work for a smaller usage case. Of
course if other people think that's important I'll be glad to work on
that alternative.

Another behavior change worth noting with this patch: the position
in history is now reset to the scratch buffer after each input
entry. Before, the position would be stay wherever it was - you didn't
restart at the "bottom" each time.

 history.c |  10 +++++-----
 enter.c   |   1 +
 history.c |  10 ++++++++++
 history.h |   1 +
 enter.c   |  10 ++++++++++
 history.c |  31 ++++++++++++++++++++++++++++---
 history.h |   2 ++
 7 files changed, 57 insertions(+), 8 deletions(-)

Mutt | 25 Apr 2013 07:25

[Mutt] #3641: Latest commit causes mutt to quit after failed password attempt on OSX 10.8.3.

#3641: Latest commit causes mutt to quit after failed password attempt on OSX
10.8.3.
------------------------+---------------------
 Reporter:  balderdash  |      Owner:  brendan
     Type:  defect      |     Status:  new
 Priority:  major       |  Milestone:
Component:  IMAP        |    Version:
 Keywords:              |
------------------------+---------------------
 Mutt from tip, OSX 10.8.3.

 Suddenly, after the April 16 commit, the following occurs (never once
 happened before):

 I do 'mutt' at the prompt to login to the IMAP server holding my mail
 (it's Zimbra).

 Next I type the incorrect password (I have $imap_pass unset).

 Next mutt says "Zimbra IMAP server terminating connection" (or something
 very similar).  Then that message disappears and I see "Login failed".

 So far, so good.  This is as it has always been and how it should be.

 But after the Apr 16th commit, this is followed up by *mutt* quitting, and
 after it's quit I see output between the last bash prompt and the new one:
 "Login failed".

 Formerly, mutt wouldn't quit, and the "Login failed" message *inside* mutt
 would stay there until I hit another key.  I could then do, for example
(Continue reading)

Mutt | 24 Apr 2013 17:43

[Mutt] #3640: Hangs on index view when connected with gmail imap server

#3640: Hangs on index view when connected with gmail imap server
---------------------+---------------------
 Reporter:  tarruda  |      Owner:  brendan
     Type:  defect   |     Status:  new
 Priority:  major    |  Milestone:
Component:  IMAP     |    Version:
 Keywords:           |
---------------------+---------------------
 Randomly hangs when connected with gmail

 When running 'strace' on the hanged mutt pid(983 in this example) I get:

     $ sudo strace -p 983
     Process 983 attached - interrupt to quit
     recv(3,

 which netstat shows to be the fd representing the IMAP connection. I also
 ran:

     $ cat /proc/983/fdinfo/3
     pos:    0
     flags:  02000002

 According to 'dalias'(#mutt on freenode) this bug seems to be related to a
 change google made in their ssl implementation about a week ago.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3640>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
(Continue reading)

Mutt | 22 Apr 2013 08:24

Re: [Mutt] #2788: <quit> in pager returns to index but should stay in pager when ask-no answered "no"

#2788: <quit> in pager returns to index but should stay in pager when ask-no
answered "no"
----------------------+------------------------------------
  Reporter:  rado     |      Owner:  kevin8t8
      Type:  defect   |     Status:  closed
  Priority:  trivial  |  Milestone:
 Component:  mutt     |    Version:  1.5.13cvs (2007-01-09)
Resolution:  fixed    |   Keywords:
----------------------+------------------------------------
Changes (by brendan):

 * status:  assigned => closed
 * resolution:   => fixed

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2788#comment:5>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Mutt | 22 Apr 2013 08:24

Re: [Mutt] #2788: <quit> in pager returns to index but should stay in pager when ask-no answered "no"

#2788: <quit> in pager returns to index but should stay in pager when ask-no
answered "no"
----------------------+------------------------------------
  Reporter:  rado     |      Owner:  kevin8t8
      Type:  defect   |     Status:  assigned
  Priority:  trivial  |  Milestone:
 Component:  mutt     |    Version:  1.5.13cvs (2007-01-09)
Resolution:           |   Keywords:
----------------------+------------------------------------

Old description:

> Per synopsis. Currently when it returns to index and re-enter pager,
> then mutt auto-scrolls down to where it was left.

New description:

 Per synopsis. Currently when it returns to index and re-enter pager,
 then mutt auto-scrolls down to where it was left.

--

Comment (by brendan):

 Applied as [d3096e8796e7]. By the way, if you include (closes #2788) in
 the changeset summary trac will automatically close the ticket and add a
 link to the changeset when it sees the changeset in the repository.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2788#comment:4>
(Continue reading)

Brendan Cully | 22 Apr 2013 08:21
Gravatar

mutt: Don't exit pager if quit=ask is answered "no".

changeset: 6305:d3096e8796e7
user:      Kevin McCarthy <kevin <at> 8t8.us>
date:      Tue Apr 16 20:12:25 2013 -0700
link:      http://dev.mutt.org/hg/mutt/rev/d3096e8796e7

Don't exit pager if quit=ask is answered "no".

This patch addresses ticket 2788.

Currently if you quit ('Q') from inside the pager, with quit=ask-yes
or quit=ask-no, and you respond "no", mutt leaves you back in the index
menu.

This patch changes it so that mutt does not exit the pager.

diffs (19 lines):

diff -r 4c5163272b9c -r d3096e8796e7 pager.c
--- a/pager.c	Thu Apr 11 02:17:41 2013 +0000
+++ b/pager.c	Tue Apr 16 20:12:25 2013 -0700
 <at>  <at>  -1927,6 +1927,15  <at>  <at> 
 	ch = -1;
 	break;

+      case OP_QUIT:
+	if (query_quadoption (OPT_QUIT, _("Quit Mutt?")) == M_YES)
+	{
+	  /* avoid prompting again in the index menu */
+	  set_quadoption (OPT_QUIT, M_YES);
+	  ch = -1;
(Continue reading)

Kevin J. McCarthy | 21 Apr 2013 04:02
Picon
Gravatar

[PATCH] Fix postpone/resume to not remove a Mail-Followup-To header

This solution changes mutt_prepare_template() to check whether the
message_id field is NULL to decide whether to wipe the message-id and
mail-followup-to headers when instantiating the message.

If we are resending a message, we don't want the previous message-id
and mail-followup-to headers.  If we are resuming a postponed message,
however, we want to keep the mail-followup-to header if any was set
before the postpone.

 postpone.c |  11 +++++++++--
 1 files changed, 9 insertions(+), 2 deletions(-)

Mutt | 17 Apr 2013 05:13

Re: [Mutt] #2788: <quit> in pager returns to index but should stay in pager when ask-no answered "no"

#2788: <quit> in pager returns to index but should stay in pager when ask-no
answered "no"
----------------------+------------------------------------
  Reporter:  rado     |      Owner:  kevin8t8
      Type:  defect   |     Status:  assigned
  Priority:  trivial  |  Milestone:
 Component:  mutt     |    Version:  1.5.13cvs (2007-01-09)
Resolution:           |   Keywords:
----------------------+------------------------------------
Changes (by kevin8t8):

 * owner:  mutt-dev => kevin8t8
 * status:  new => assigned

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2788#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Kevin J. McCarthy | 17 Apr 2013 05:12
Picon
Gravatar

[PATCH] Don't exit pager if quit=ask is answered "no"

This patch addresses ticket 2788.

Currently if you quit ('Q') from inside the pager, with quit=ask-yes
or quit=ask-no, and you respond "no", mutt leaves you back in the index
menu.

This patch changes it so that mutt does not exit the pager.

 pager.c |  9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)


Gmane