Christophe TROESTLER | 2 Nov 2009 10:03
X-Face
Picon

[mew-int 2754] Re: Mew 6.3 release candidate 2

Hi,

On Mon, 2 Nov 2009 13:53:23 +0900, Kazu Yamamoto wrote:
> 
> I have released Mew 6.3 release candidate 2:
> 	http://www.mew.org/Beta/mew-6.3rc2.tar.gz
> 
> After rc1 was released, one bug of choosing *minimum* charset appeared
> on Emacs 23. This is because Emacs 23 does not maintain backward
> compatibility, sigh. I have fixed this bug, so rc2.

Thanks for your work on this.  I am sorry I did not have time to test
your patch earlier.  I now upgraded to the latest CVS version and I
confirm that it works for iso-8859-1.  However, when, say, the "€"
symbol is present, Mew selects euc-kr instead of iso-8859-15.  Maybe
just a little bit of fine tuning will do??

Best,
Christophe

Bernhard Assmann | 2 Nov 2009 13:42

[mew-int 2755] stunnel: decompression failure

Hi,

I'm trying to connect to an IMAP-Server over SSL, but only every other connect
is successful. Doing the same operation twice is a little bit tedious. I'm
using mew 6.3rc2 on Emacs 22.2.

Any hints?

Thanks

Bernhard

====================

Mew debug buffer from an unsuccessful attempt

<SSL/TLS: >
2009.11.02 09:55:36 LOG7[12058:4156889840]: 9612 accepted FD=11 from 127.0.0.1:18947
2009.11.02 09:55:36 LOG7[12058:4160359312]: 9612 started
2009.11.02 09:55:36 LOG7[12058:4160359312]: FD 11 in non-blocking mode
2009.11.02 09:55:36 LOG7[12058:4160359312]: Waiting for a libwrap process
2009.11.02 09:55:36 LOG7[12058:4160359312]: Acquired libwrap process #0
2009.11.02 09:55:36 LOG7[12058:4160359312]: Releasing libwrap process #0
2009.11.02 09:55:36 LOG7[12058:4160359312]: Released libwrap process #0
2009.11.02 09:55:36 LOG7[12058:4160359312]: 9612 permitted by libwrap from 127.0.0.1:18947
2009.11.02 09:55:36 LOG5[12058:4160359312]: 9612 accepted connection from 127.0.0.1:18947
2009.11.02 09:55:36 LOG7[12058:4160359312]: FD 12 in non-blocking mode
2009.11.02 09:55:36 LOG7[12058:4160359312]: 9612 connecting xxx.xxx.xxx.xxx:993
2009.11.02 09:55:36 LOG7[12058:4160359312]: connect_wait: waiting 10 seconds
2009.11.02 09:55:36 LOG7[12058:4160359312]: connect_wait: connected
(Continue reading)

Kazu Yamamoto | 3 Nov 2009 13:28
Picon
Gravatar

[mew-int 2756] Re: Mew 6.3 release candidate 2

Hello,

> Thanks for your work on this.  I am sorry I did not have time to test
> your patch earlier.  I now upgraded to the latest CVS version and I
> confirm that it works for iso-8859-1.  However, when, say, the "€"
> symbol is present, Mew selects euc-kr instead of iso-8859-15.  Maybe
> just a little bit of fine tuning will do??

Please apply the following patch to rc2 and test it.

--Kazu

Index: mew-mule3.el
===================================================================
RCS file: /cvsroot/mew/mew/mew-mule3.el,v
retrieving revision 1.55
diff -c -r1.55 mew-mule3.el
*** mew-mule3.el	2 Nov 2009 04:39:09 -0000	1.55
--- mew-mule3.el	3 Nov 2009 12:27:32 -0000
***************
*** 197,215 ****

  (if (fboundp 'set-charset-priority)
      (defun mew-find-cs-region (beg end)
!       (let ((charset-list (charset-priority-list)))
! 	(set-charset-priority 'japanese-jisx0208 'korean-ksc5601
! 			      'latin-iso8859-1 'latin-iso8859-2
! 			      'latin-iso8859-3 'latin-iso8859-4
! 			      'cyrillic-iso8859-5 'greek-iso8859-7
! 			      'hebrew-iso8859-8 'latin-iso8859-9
(Continue reading)

Harald Barth | 3 Nov 2009 16:49
Picon
Picon
Favicon

[mew-int 2757] Searching in encoded Subject: lines?


Hi!

I run Mew 5.2.51 and I am quite happy with it (thanks Kazu). I wonder
if the 6.3 code includes improved search. With "improved" I mean than
when I type "/subject=Anders" and the email has

(example, Subject: =?ISO-8859-1?B?UmU6IEFuZGVycyAiR3J1c2lzIiBmeWxsZXIg5XIu?= )

then the search will not find it. However, in the summary, subject is
decoded correctly, 

(example, Subject: Re: Anders "Grusis" fyller år. )

so I can find it in the emacs buffer, using Ctrl-r.
That does not work for parts of the subject that are longer than the
X displayed characters.

Thanks,
Harald.

maxigas | 4 Nov 2009 01:38
Gravatar

[mew-int 2758] Re: answering and email results in strange buffer arrangement

From: Michael Ernst <mernst <at> cs.washington.edu>
Subject: [mew-int 2741] Re: answering and email results in strange buffer arrangement
Date: Sun, 04 Oct 2009 17:27:00 -0700 (PDT)

>> i just realised that when i hit "a" for answering an email in mew i
>> get a strange layout of emacs buffers.  what happens is that rather
>> than having three horizontal buffers like usual (list of email on
>> the top, original email in the middle, draft where i compose the
>> answer in the bottom), the bottom side of the screen is vertically
>> divided between another list view and the draft email.
> 
> This is not related to Mew.  It is standard Emacs 23 behavior.
> 
> The Emacs 23 NEWS file states:
> 
>   ** Changes affecting display-buffer
> 
>   *** display-buffer tries to be smarter when splitting windows.
>   The new option split-window-preferred-function lets you specify your own
>   function to pop up new windows.  Its default value split-window-sensibly
>   can split a window either vertically or horizontally, whichever seems
>   more suitable in the current configuration.  You can tune the behavior
>   of split-window-sensibly by customizing split-height-threshold and the
>   new option split-width-threshold.  Both options now take the value nil
>   to inhibit splitting in one direction.  Setting split-width-threshold to
>   nil inhibits horizontal splitting and gets you the behavior of Emacs 22
>   in this respect.  In any case, display-buffer may now split the largest
>   window vertically even when it is not as wide as the containing frame.
> 
> You can read the NEWS file by typing  C-h C-n.  This will tell you about
(Continue reading)

Kazu Yamamoto | 4 Nov 2009 07:33
Picon
Gravatar

[mew-int 2759] Re: stunnel: decompression failure

> I'm trying to connect to an IMAP-Server over SSL, but only every other connect
> is successful. Doing the same operation twice is a little bit tedious. I'm
> using mew 6.3rc2 on Emacs 22.2.

I guess your IMAP server has both IPv4 and IPv6 addresses but the IMAP
service is provided only on IPv4...
Or it has two IPv4 addresses and only one of them provides IMAP.

--Kazu

Kazu Yamamoto | 4 Nov 2009 08:24
Picon
Gravatar

[mew-int 2760] Re: Searching in encoded Subject: lines?

Hello,

> I run Mew 5.2.51 and I am quite happy with it (thanks Kazu). I wonder
> if the 6.3 code includes improved search. 

The answer is No. Sorry.

I'm planning to implment DB for mail search from scratch. But it will
take a long time...

--Kazu

Christophe TROESTLER | 5 Nov 2009 11:42
X-Face
Picon

[mew-int 2761] Re: Mew 6.3 release candidate 2

Hi,

On Tue, 3 Nov 2009 21:28:39 +0900, Kazu Yamamoto wrote:
> 
> Please apply the following patch to rc2 and test it.

It works... but now Mew always select iso-8859-15 regardless of the
preference set with mew-charset-latin.  A slight modification to your
patch will probably do.

Best,
Christophe

Michael Ernst | 7 Nov 2009 01:51
Favicon

[mew-int 2762] Patch: 2 cross-references for manual

This patch adds 2 cross-references to the Mew manual (the English version
only).  These help the reader to understand the Summary Mode display.

The patch also fixes a typo.

                    -Michael Ernst

--- mew.texi.~1.366.~	2009-11-04 09:39:56.000000000 -0800
+++ mew.texi	2009-11-06 16:50:54.000000000 -0800
 <at>  <at>  -317,7 +317,7  <at>  <at> 
 Mew には次の 7 つのモードがあります。
  <at> end ifset
  <at> ifset us
-Mew has the following six modes:
+Mew has the following seven modes:
  <at> end ifset

  <at> table  <at> samp
 <at>  <at>  -1029,7 +1029,7  <at>  <at> 
  <at> end ifset
  <at> ifset us
 As you can see the example above, the format of Summary mode consists of
-a mark, data type (a mark by Mew), date, a sender, Subject:, and a body.
+a mark ( <at> pxref{Marks}), data type (a mark by Mew,  <at> pxref{mew-mark}), date, a sender, Subject:, and a body.
  <at> end ifset

  <at> ifset jp

Kazu Yamamoto | 11 Nov 2009 08:56
Picon
Gravatar

[mew-int 2763] Re: Mew 6.3 release candidate 2

> It works... but now Mew always select iso-8859-15 regardless of the
> preference set with mew-charset-latin.  A slight modification to your
> patch will probably do.

Please apply the following patch to pure RC2 and test it.

Since Emacs 23 does not maintain backward compatibility to Emacs 22,
it is very difficult to maintain semantics of mew-charset-latin on
Emacs 23. So, the patch prefers iso-8859-1 to iso-8859-15 always.

i.e.

1-only-characters        -> iso-8859-1
15-only-characters       -> iso-8859-15
both-1-and-15-characters -> iso-8859-1                      <== take care
1-only-characters both-1-and-15-characters  -> iso-8859-1
15-only-characters both-1-and-15-characters -> iso-8859-15
1-only-characters 15-only-characters both-1-and-15-characters -> utf-8

--Kazu

Index: mew-mule.el
===================================================================
RCS file: /cvsroot/mew/mew/mew-mule.el,v
retrieving revision 1.28
retrieving revision 1.29
diff -c -r1.28 -r1.29
*** mew-mule.el	21 Jan 2009 05:54:56 -0000	1.28
--- mew-mule.el	11 Nov 2009 07:47:56 -0000	1.29
***************
(Continue reading)


Gmane