[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: reproducable hang with non-ascii characters in Wanderlust draft
- To: wl-en@lists.airs.net
- Subject: Re: reproducable hang with non-ascii characters in Wanderlust draft
- From: "Herbert J. Skuhra" <h.skuhra@gmail.com>
- Date: Sat, 06 Feb 2010 17:11:53 +0100
- Delivered-to: wl-en@lists.airs.net
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:references:user-agent:mime-version:content-type :content-transfer-encoding; bh=L855tX8iXRXLN+gUC82T6XAMOCPkNctHYWFHymE9iRc=; b=NELbCv2B21y5ybMibsS9ZerJzxB45JqdWswafVA3RgLb35qEtyjQ3XPzw7YREy3QP6 EVfc8FIm/0Z6q3wtO+vHKbyKPjN3nL1w6Er+FjIVOzaL0qEwa21ynbqPHYbGGngzgibk bnhnLZWF4Y3FXb+cNbjcB0WQlqe7uZCoOSrZg=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:references:user-agent :mime-version:content-type:content-transfer-encoding; b=KNoi2xnoEgJjh5vVfWjhTdGuo9vyEaHsjUsS+IalvOdp1AJSo5tloMcql1pHC3/6Kc xXmp2LHJdmqwe3+FRvuW8f4t392bktmDTUpilESmE2LvUdSBmzGUyEFZ3QRMmKtpxm/m GL549vq7FbXa6ZHtlk3kDLlwgsl3lBaaGKgQE=
- In-reply-to: <873a1e7fgz.wl%djcb@djcbsoftware.nl>
- List-help: <mailto:wl-en-ctl@lists.airs.net?body=help>
- List-id: wl-en.lists.airs.net
- List-owner: <mailto:wl-en-admin@lists.airs.net>
- List-post: <mailto:wl-en@lists.airs.net>
- List-software: fml [fml stable 20011102.2100]
- List-unsubscribe: <mailto:wl-en-ctl@lists.airs.net?body=unsubscribe>
- References: <873a1e7fgz.wl%djcb@djcbsoftware.nl>
- Reply-to: wl-en@lists.airs.net
- User-agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.7 Emacs/23.1.92 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)
At Sat, 06 Feb 2010 13:47:56 +0200,
Dirk-Jan C. Binnema wrote:
>
> Hi,
>
> I've been mentioning this bug before, but finally I have some easy steps to
> reproduce, plus a backtrace. I've seen this problem with the Ubuntu-packaged
> versions of wl-beta and emacs23, and now reproduced this with a recent bzr
> built of emacs and the wl packages as built from Dave Abrahams' git repo.
>
> The procedure to reproduce (in my case) are quite easy: type some non-ascii
> characters in a draft message in Wanderlust, something like
>
> äëïöÿüäëïöüÿäëïöüÿäëïöüÿäëïöüÿäëïöüÿäëïöüÿäëïöüÿäëïöüÿäëïöüÿäëïöüÿäëïöüÿäëïöü
>
> Try to save the draft (C-x s). This works. Now, copy the line about 50 times,
> so you have a whole block of these characters. If I now try to save, emacs
> gets very busy (CPU goes to the max), and it never seems to recover (waited
> for at least 15 minutes), and I have to kill emacs. See the attached backtrace
> - it was from an -O2 build, but I hope it contains enough info for those in
> the know.
>
> Note, I get this this same behavior in perfectly normal e-mails with only a
> few of these non-ascii characters.
>
> Before, someone suggested using
> (mel-use-module 'mel-q '("quoted-printable" "Q"))
> however, that gives me an error instead:
> insert: Args out of range: "0123456789ABCDEF", 262140
> and refuses to save.
>
> I suspect something changed in Emacs 23 and Wanderlust (or flim, semi, apel)
> do not play nice with that.
>
> Any kind of solution would be much appreciated.
Stop using 7bit quoted-printable by adding the following line to your ~/.wl:
(setq-default mime-transfer-level 8)
Use an external qp encoder. I've added the following lines to my
~/.emacs:
(setq mel-b-ccl-module nil)
(setq mel-q-ccl-module nil)
(setq base64-external-encoder '("mimencode"))
(setq base64-external-decoder '("mimencode" "-u"))
(setq base64-external-decoder-option-to-specify-file '("-o"))
(setq quoted-printable-external-encoder '("mimencode" "-q"))
(setq quoted-printable-external-decoder '("mimencode" "-q" "-u"))
(setq quoted-printable-external-decoder-option-to-specify-file '("-o"))
(setq base64-internal-decoding-limit 0)
(setq base64-internal-encoding-limit 0)
(setq quoted-printable-internal-decoding-limit 0)
(setq quoted-printable-internal-encoding-limit 0)
But now I have problems with wl-summary-reply-with-citation.
-Herbert