Mutt | 2 Apr 2008 13:24

[Mutt] #3043: pressing 'y' after starting 'mutt -y' exits

#3043: pressing 'y' after starting 'mutt -y' exits

 Run mutt using 'mutt -y'
 press 'y' while in mutt

 mutt quits immediately returning 0

 tested using trivial config file:

 $ cat .mutt/muttrc
 mailboxes ~/Mail
 $

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3043>

Michael Tatge | 3 Apr 2008 01:58
Picon

Re: [Mutt] #3043: pressing 'y' after starting 'mutt -y' exits

* On Wed, Apr 02, 2008 Mutt wrote:
> #3043: pressing 'y' after starting 'mutt -y' exits
> 
>  Run mutt using 'mutt -y'
>  press 'y' while in mutt
> 
>  mutt quits immediately returning 0

I only get "Key is not bound as expected.

Michael

Mutt | 3 Apr 2008 02:01

Re: [Mutt] #3043: pressing 'y' after starting 'mutt -y' exits

#3043: pressing 'y' after starting 'mutt -y' exits

Comment (by Michael Tatge):

 {{{
 * On Wed, Apr 02, 2008 Mutt wrote:
 > #3043: pressing 'y' after starting 'mutt -y' exits
 >
 >  Run mutt using 'mutt -y'
 >  press 'y' while in mutt
 >
 >  mutt quits immediately returning 0

 I only get "Key is not bound as expected.

 Michael
 }}}

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3043#comment:>

Mutt | 3 Apr 2008 08:56

Re: [Mutt] #3043: pressing 'y' after starting 'mutt -y' exits

#3043: pressing 'y' after starting 'mutt -y' exits

Comment (by ):

 {{{
 On Thu, Apr 03, 2008 at 12:01:17AM -0000, Mutt wrote:
 > #3043: pressing 'y' after starting 'mutt -y' exits
 >
 > Comment (by Michael Tatge):
 >
 >  {{{
 >  * On Wed, Apr 02, 2008 Mutt wrote:
 >  > #3043: pressing 'y' after starting 'mutt -y' exits
 >  >
 >  >  Run mutt using 'mutt -y'
 >  >  press 'y' while in mutt
 >  >
 >  >  mutt quits immediately returning 0
 >
 >  I only get "Key is not bound as expected.
 >
 >  Michael
 >  }}}

 hmmm strange.
 I made sure to use a blank configuration screen.
 Maybe it's debian's default key bindings?

 ||/ Name           Version        Description
 +++-==============-==============-============================================
(Continue reading)

Michael Tatge | 3 Apr 2008 09:15
Picon

Re: [Mutt] #3043: pressing 'y' after starting 'mutt -y' exits

* On Thu, Apr 03, 2008 Mutt wrote:
> #3043: pressing 'y' after starting 'mutt -y' exits
> 
> Comment (by ):
>  {{{
>  On Thu, Apr 03, 2008 at 12:01:17AM -0000, Mutt wrote:
>  > Comment (by Michael Tatge):
>  >  {{{
>  >  * On Wed, Apr 02, 2008 Mutt wrote:
>  >  I only get "Key is not bound as expected.
> 
>  hmmm strange.
>  I made sure to use a blank configuration screen.
>  Maybe it's debian's default key bindings?
> 
>  ||/ Name           Version        Description
>  +++-==============-==============-============================================
>  ii  mutt           1.5.17+2008011 text-based mailreader supporting MIME,
>  }}}

So you have 1.5.17, i still use 1.5.16. Maybe the bug was introduced in
.17.
Just to make sure run »mutt -n -F /dev/null -e 'mailboxes
[/path/to/existing/mailbox]' -y«

Michael

Mutt | 3 Apr 2008 09:15

Re: [Mutt] #3043: pressing 'y' after starting 'mutt -y' exits

#3043: pressing 'y' after starting 'mutt -y' exits

Comment (by Michael Tatge):

 {{{
 * On Thu, Apr 03, 2008 Mutt wrote:
 > #3043: pressing 'y' after starting 'mutt -y' exits
 >
 > Comment (by ):
 >  {{{
 >  On Thu, Apr 03, 2008 at 12:01:17AM -0000, Mutt wrote:
 >  > Comment (by Michael Tatge):
 >  >  {{{
 >  >  * On Wed, Apr 02, 2008 Mutt wrote:
 >  >  I only get "Key is not bound as expected.
 >
 >  hmmm strange.
 >  I made sure to use a blank configuration screen.
 >  Maybe it's debian's default key bindings?
 >
 >  ||/ Name           Version        Description
 >
 +++-==============-==============-============================================
 >  ii  mutt           1.5.17+2008011 text-based mailreader supporting
 MIME,
 >  }}}

 So you have 1.5.17, i still use 1.5.16. Maybe the bug was introduced in
 .17.
 Just to make sure run »mutt -n -F /dev/null -e 'mailboxes
(Continue reading)

Mutt | 3 Apr 2008 09:51

Re: [Mutt] #3043: pressing 'y' after starting 'mutt -y' exits

#3043: pressing 'y' after starting 'mutt -y' exits

Comment (by ):

 {{{
 On Thu, Apr 03, 2008 at 07:15:40AM -0000, Mutt wrote:
 >  So you have 1.5.17, i still use 1.5.16. Maybe the bug was introduced in
 >  .17.
 >  Just to make sure run »mutt -n -F /dev/null -e 'mailboxes
 >  [/path/to/existing/mailbox]' -y«
 >
 >  Michael

 the '-n' flag solves the problem.
 After looking at debian's /etc/Muttrc I came across:

 [...]
 bind browser y exit
 [...]

 sorry for not investigating this further in the first place!
 You can close the bug

 Thanks!
 }}}

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3043#comment:>

(Continue reading)

Miroslav Lichvar | 3 Apr 2008 18:02
Picon
Favicon

[PATCH] Fix sending long commands when using gnutls

Hi,

mutt (with enabled gnutls support) hangs when trying to send IMAP
commands longer than 16KB. This is caused by gnutls_record_send(),
which returns after sending one message block instead of sending all
data from the buffer.

# HG changeset patch
# User Miroslav Lichvar <mlichvar <at> redhat.com>
# Date 1207235293 -7200
# Branch HEAD
# Node ID c10d4343a17f8576e1f99b795c3ac53d01043279
# Parent  e3bc99a4a6bde15d0c411b557d1dec6f8596f499
Fix sending long commands when using gnutls.

diff -r e3bc99a4a6bd -r c10d4343a17f mutt_ssl_gnutls.c
--- a/mutt_ssl_gnutls.c	Tue Mar 11 17:20:48 2008 -0700
+++ b/mutt_ssl_gnutls.c	Thu Apr 03 17:08:13 2008 +0200
 <at>  <at>  -112,6 +112,7  <at>  <at>  static int tls_socket_write (CONNECTION*
 {
   tlssockdata *data = conn->sockdata;
   int ret;
+  size_t sent = 0;

   if (!data)
   {
 <at>  <at>  -120,14 +121,23  <at>  <at>  static int tls_socket_write (CONNECTION*
     return -1;
   }

(Continue reading)

Mutt | 3 Apr 2008 20:49

Re: [Mutt] #3043: pressing 'y' after starting 'mutt -y' exits

#3043: pressing 'y' after starting 'mutt -y' exits

Changes (by brendan):

  * status:  new => closed
  * resolution:  => invalid

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3043#comment:5>

Vincent Lefevre | 5 Apr 2008 17:13

Re: [Mutt] #3040: charset difference between index browser and

On 2008-03-28 09:48:02 -0400, Derek Martin wrote:
> switch your environment to UTF-8.  So who's the idiot?

You're not living in the real world. How can one switch the Zaurus
to UTF-8? How can one switch the environment to UTF-8 when UTF-8
locales have not been installed and the user isn't root and the
admins are not responsive?

There are also many bugs related to UTF-8, e.g. Debian bug 391452
(that's the most important one), Debian bug 254507, cooked mode
under Mac OS X, all these bugs with combining characters (they
occur much more often when using Mac OS X). Also, emacs22 isn't
in Debian/stable yet, and emacs21 is very broken under UTF-8
locales (in particular, copy-paste doesn't work). I've started to
switch to UTF-8, but I'm fed up with all these bugs I encounter,
so that I'm still mainly under ISO-8859-1 locales.

Another main problem: Most of my files are in ISO-8859-1. And things
like grep wouldn't work under UTF-8 (is there any wrapper?).

Also, latex is reported to have problems with UTF-8 files, though
I haven't tried it myself.

> > With Emacs, I can, even in ISO-8859-1 locales. 
> 
> You can view Japanese characters in Emacs running in an xterm with
> ISO-8859-1 settings and fonts?  I sincerely doubt that...

Most of the time, I use Emacs under ISO-8859-1 in its own window.
So, I can view non-ISO-8859-1 characters without any problem.
(Continue reading)


Gmane