From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: RMAIL, MIME-related bug Date: 20 Oct 2003 08:15:18 +0300 Organization: JURTA Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <873cdotrq1.fsf@mail.jurta.org> References: <200310121947.h9CJlhKH006102@oak.pohoyda.family> <874qy4vbg7.fsf@mail.jurta.org> <200310200418.NAA04336@etlken.m17n.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1066627418 21256 80.91.224.253 (20 Oct 2003 05:23:38 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 20 Oct 2003 05:23:38 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Oct 20 07:23:35 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1ABSVz-0002ZW-00 for ; Mon, 20 Oct 2003 07:23:35 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1ABSVz-0005eG-00 for ; Mon, 20 Oct 2003 07:23:35 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ABSSU-0005rE-PV for emacs-devel@quimby.gnus.org; Mon, 20 Oct 2003 01:19:58 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1ABSSP-0005r9-JW for emacs-devel@gnu.org; Mon, 20 Oct 2003 01:19:53 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1ABSRt-0005aM-Cr for emacs-devel@gnu.org; Mon, 20 Oct 2003 01:19:52 -0400 Original-Received: from [64.246.52.232] (helo=ns5.tangramltd.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.24) id 1ABSRs-0005aJ-Vq for emacs-devel@gnu.org; Mon, 20 Oct 2003 01:19:21 -0400 Original-Received: from 80-235-32-99-dsl.mus.estpak.ee ([80.235.32.99] helo=mail.jurta.org) by ns5.tangramltd.com with esmtp (Exim 4.20) id 1ABSRo-0002nF-OT; Mon, 20 Oct 2003 08:19:17 +0300 Original-To: Kenichi Handa In-Reply-To: <200310200418.NAA04336@etlken.m17n.org> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Original-Lines: 43 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ns5.tangramltd.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jurta.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:17253 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:17253 Kenichi Handa writes: > Juri Linkov writes: > > I see one solution to these problems - to export entire mbox to the > > file system, i.e. to save MIME parts to separate files, decode > > base64/quoted-printable regions, convert the charset from Content-Type > > line to Emacs encoding, add corresponding -*- coding: -*- line, and > > save fully decoded message to a separate file. > > > Note that this don't contradict the decision to store messages in mbox > > in their undecoded form. The proposed solution duplicates the content > > of messages in the decoded form. Hard disks now so cheap that having > > two copies of the same message is not a problem. The decoded messages > > could also be used as a cache to make displaying messages faster, > > whereas undecoded messages will be available to resend forwards, where > > no original information should be lost. There should be some way to > > correlate between them, i.e. to find corresponding decoded message > > from undecoded one, and vice versa. > > This method is very similar to what I proposed in my > previous mail. > > Kenichi Handa writes: > > (1) Read RMAIL file without decoding into some hidden source > > buffer (unibyte). It may be ok to process only > > Content-Transfer-Encoding. > > (2) Prepare a view buffer. > > (3) Insert the current message in the view buffer after decoding it. > > (4) A background process (run by idle timer?) decodes not > > yet decoded message into the view buffer (like > > jit-lock-stealth-fontify). > > Mine doesn't save the view buffer in a file, yours does. Yes, this method is very similar to yours. However, I added saving of decoded messages in files to solve the mentioned problems: 1. Mail archives with fully decoded messages can be grepped, if they are stored in files; 2. It's possible to refer to separate messages as to ordinary files. -- http://www.jurta.org/emacs/