headers
Vincent Lefevre | 1 Jul 05:33
Gravatar

Re: SIGQUIT (what the...?)

On 2009-06-29 19:07:45 -0500, Derek Martin wrote:
> I found that ^4 causes Mutt to receive SIGQUIT.  Then I tried some
> other terminal-oriented program, and pressing ^4 there also generated
> a SIGQUIT.

Yes, it seems that ^3 to ^7 generate ASCII chars 27 to 31 (and NUL
for ^2).

--

-- 
Vincent Lefèvre <vincent <at> vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
Permalink | Reply | 0 comments |
headers
Brendan Cully | 1 Jul 09:00
Gravatar

mutt: 2 new changesets

2 new changesets in mutt:

http://dev.mutt.org/hg/mutt/rev/f4baa2f1251a
changeset:   5962:f4baa2f1251a
branch:      HEAD
tag:         tip
user:        Rocco Rutte <pdmef <at> gmx.net>
date:        Tue Jun 30 17:32:55 2009 +0200
summary:     Add missing config.h include to pgpewrap.c

http://dev.mutt.org/hg/mutt/rev/7c8f018d33a5
changeset:   5961:7c8f018d33a5
branch:      HEAD
user:        Rocco Rutte <pdmef <at> gmx.net>
date:        Tue Jun 30 17:31:44 2009 +0200
summary:     Manual: Run lynx with --display_charset=us-ascii, see #3286.

--

-- 
Repository URL: http://dev.mutt.org/hg/mutt
Permalink | Reply | 0 comments |
headers
Mutt | 1 Jul 09:01

Re: [Mutt] #1317: wish $edit_charset

#1317: wish $edit_charset
------------------------------------------------+---------------------------
  Reporter:  Tony Leneis <tony <at> cvr.ds.adp.com>  |       Owner:  mutt-dev
      Type:  enhancement                        |      Status:  new     
  Priority:  minor                              |   Milestone:          
 Component:  charset                            |     Version:  1.4i    
Resolution:                                     |    Keywords:          
------------------------------------------------+---------------------------

Comment(by Derek Martin):

 {{{
 The author of this wish list item is complaining that if he uses
 ISO-8859-1, he can't retain curly quotes in his replies.  ISO-8859-1
 has none; he's dealing with a misconfigured Windows mailer that's
 labeling Windows-1252 (or similar) as ISO-8859-1.  This is a
 suggestion to add a gross hack to work around a brokenness in another
 program...  His problem would be solved correctly by switching to
 UTF-8, or just accepting that ISO-8859-1 just doesn't have curly
 quotes.  This "bug" is 7 years old, and there remain few genuine
 obstacles to adopting UTF-8.

 Vincent suggests this is a bug...  It's not; the conversion only
 happens when using //translit to represent characters that don't
 actually exist in the given encoding.  If Mutt is going to send the
 message out as ISO-8859-1, leaving the curly quotes in *would* be a
 bug, since they don't exist in that encoding.

 I think this should be closed.
 }}}
(Continue reading)

Permalink | Reply | 28 comments |
headers
Vincent Lefevre | 1 Jul 09:36
Gravatar

Re: [Mutt] #1317: wish $edit_charset

>  The author of this wish list item is complaining that if he uses
>  ISO-8859-1, he can't retain curly quotes in his replies.  ISO-8859-1
>  has none; he's dealing with a misconfigured Windows mailer that's
>  labeling Windows-1252 (or similar) as ISO-8859-1.  This is a
>  suggestion to add a gross hack to work around a brokenness in another
>  program...

No, you did not understand the problem and what the user wants. The
user wants to edit the message in UTF-8 even though his terminal uses
another charset. This is possible with most editors nowadays: they
can handle UTF-8 internally, even though the locale is something
like ISO-8859-1. If such an editor uses its own window, then it will
ignore the locale there (it can display UTF-8). If the editor uses
the terminal window, it does charset translation/transliteration for
the *display* only; internally, the original UTF-8 characters remain
intact.

Note that this is an option: the user will not be forced to use a
different charset for the terminal and for the file to be edited.

> This "bug" is 7 years old, and there remain few genuine obstacles to
> adopting UTF-8.

There are still some places where UTF-8 is badly handled, e.g.
in terminals. Also I move from time to time and I sometimes use
other people's machines to read my mail via ssh; and UTF-8 isn't
always available.

--

-- 
Vincent Lefèvre <vincent <at> vinc17.org> - Web: <http://www.vinc17.org/>
(Continue reading)

Permalink | Reply | 27 comments |
headers
Mutt | 1 Jul 09:36

Re: [Mutt] #1317: wish $edit_charset

#1317: wish $edit_charset
------------------------------------------------+---------------------------
  Reporter:  Tony Leneis <tony <at> cvr.ds.adp.com>  |       Owner:  mutt-dev
      Type:  enhancement                        |      Status:  new     
  Priority:  minor                              |   Milestone:          
 Component:  charset                            |     Version:  1.4i    
Resolution:                                     |    Keywords:          
------------------------------------------------+---------------------------

Comment(by Vincent Lefevre):

 {{{

 No, you did not understand the problem and what the user wants. The
 user wants to edit the message in UTF-8 even though his terminal uses
 another charset. This is possible with most editors nowadays: they
 can handle UTF-8 internally, even though the locale is something
 like ISO-8859-1. If such an editor uses its own window, then it will
 ignore the locale there (it can display UTF-8). If the editor uses
 the terminal window, it does charset translation/transliteration for
 the *display* only; internally, the original UTF-8 characters remain
 intact.

 Note that this is an option: the user will not be forced to use a
 different charset for the terminal and for the file to be edited.

 There are still some places where UTF-8 is badly handled, e.g.
 in terminals. Also I move from time to time and I sometimes use
 other people's machines to read my mail via ssh; and UTF-8 isn't
 always available.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jul 10:02

Re: [Mutt] #3150: garbage display with combining characters and

#3150: garbage display with combining characters and Mutt's wc functions
(--without-wc-funcs)
----------------------+-----------------------------------------------------
  Reporter:  vinc17   |       Owner:  mutt-dev
      Type:  defect   |      Status:  new     
  Priority:  major    |   Milestone:  1.6     
 Component:  charset  |     Version:          
Resolution:           |    Keywords:          
----------------------+-----------------------------------------------------

Comment(by vinc17):

 The problem occurs when I use
 {{{
 set charset=UTF-8//TRANSLIT
 }}}
 Note: I could modify the script that sets my $charset to avoid the useless
 //TRANSLIT in case of UTF-8, but this is still a bug.

 Anyway, output is also incorrect with
 {{{
 set charset=UTF-8
 }}}
 though more readable. In a 80-column terminal, I get
 {{{
 é.1 é.2 é.3 é.4 é.5 é.6 é.7 é.8 é.9 é.10 é.11 é.12 é.13 é.14 é.15
  é.16 é.17 é.18+é.19 é.20
 }}}
 instead of
 {{{
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mutt | 1 Jul 12:47

[Mutt] #3287: imap recent not honoured

#3287: imap recent not honoured
---------------------------------------+------------------------------------
 Reporter:  prlw1                      |       Owner:  brendan
     Type:  defect                     |      Status:  new    
 Priority:  major                      |   Milestone:         
Component:  IMAP                       |     Version:  1.5.20 
 Keywords:  recent status noop exists  |  
---------------------------------------+------------------------------------
 eg:

 {{{
 4> a0006 NOOP^M
 4< * 223258 EXISTS
 Handling EXISTS
 cmd_handle_untagged: New mail in INBOX - 223258 messages total.
 4< * 205 RECENT
 4< a0006 OK Completed
 IMAP queue drained
 }}}

 but mutt says New:4
 which are the 4 messages which arrived while mutt was running i.e., not
 including the 205 which arrived since mutt had last viewed the inbox.

 I am not using the header cache, and this is against a cyrus imap server.
 Using today's (1st July) mercurial source.

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3287>
Mutt <http://www.mutt.org/>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mutt | 1 Jul 16:28

Re: [Mutt] #3284: body cache depends on $charset

#3284: body cache depends on $charset
-------------------------+--------------------------------------------------
  Reporter:  pdmef       |       Owner:  pdmef   
      Type:  defect      |      Status:  accepted
  Priority:  minor       |   Milestone:  1.6     
 Component:  body cache  |     Version:  1.5.20  
Resolution:              |    Keywords:          
-------------------------+--------------------------------------------------
Changes (by pdmef):

  * status:  new => accepted

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3284#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Mutt | 1 Jul 16:28

Re: [Mutt] #3284: body cache depends on $charset

#3284: body cache depends on $charset
-------------------------+--------------------------------------------------
  Reporter:  pdmef       |       Owner:  pdmef  
      Type:  defect      |      Status:  started
  Priority:  minor       |   Milestone:  1.6    
 Component:  body cache  |     Version:  1.5.20 
Resolution:              |    Keywords:         
-------------------------+--------------------------------------------------
Changes (by pdmef):

  * status:  accepted => started

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3284#comment:4>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |
headers
Mutt | 1 Jul 16:29

Re: [Mutt] #3282: mutt does not honour --docdir

#3282: mutt does not honour --docdir
---------------------+------------------------------------------------------
  Reporter:  sahko   |       Owner:  pdmef  
      Type:  defect  |      Status:  started
  Priority:  minor   |   Milestone:  1.6    
 Component:  build   |     Version:  1.5.20 
Resolution:          |    Keywords:         
---------------------+------------------------------------------------------
Changes (by pdmef):

  * status:  accepted => started

--

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3282#comment:5>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
Permalink | Reply | 0 comments |

Gmane