unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: monnier+gnu/emacs@rum.cs.yale.edu,
	monnier+gnu/emacs@rum.cs.yale.edu, eliz@is.elta.co.il,
	emacs-devel@gnu.org, pmr@pajato.com
Subject: Re: Rmail changes for Emacs 22
Date: Fri, 25 Oct 2002 01:36:26 -0400	[thread overview]
Message-ID: <E184x90-0003vI-00@fencepost.gnu.org> (raw)
In-Reply-To: <200210230813.RAA16342@etlken.m17n.org> (message from Kenichi Handa on Wed, 23 Oct 2002 17:13:58 +0900 (JST))

    (1) A simple way:

    Decode only when we need the contents of a message (e.g. for
    displaying or searching).

    This may be slow on searching all messages repeatedly.

This could be a good point about searching.  But maybe computers
now are so fast that it is ok.

We should try to avoid all methods that use more than one buffer.

Another idea is to decode all the messages when the contents are
wanted the first time, and leave the decoded message in the buffer in
place of the original.  The original could be found in the file if
needed (if the user gives a command to "please decode again with a
different coding system").

  reply	other threads:[~2002-10-25  5:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <rzqu1jseva6.fsf@albion.dl.ac.uk>
2002-10-13  4:08 ` Rmail changes for Emacs 22 Richard Stallman
2002-10-15 17:40   ` Dave Love
2002-10-16  4:38     ` Richard Stallman
2002-10-16  6:09       ` Eli Zaretskii
2002-10-16  7:19         ` Kenichi Handa
2002-10-19  4:25           ` Paul Michael Reilly
2002-10-19  4:55           ` Richard Stallman
2002-10-20  7:03             ` Eli Zaretskii
2002-10-18 22:59         ` Richard Stallman
2002-10-20 19:40           ` Stefan Monnier
2002-10-22  3:12             ` Richard Stallman
2002-10-22  6:33               ` Kai Großjohann
2002-10-22 18:48                 ` Eli Zaretskii
2002-10-22 14:32               ` Stefan Monnier
2002-10-23  7:12                 ` Richard Stallman
2002-10-23  8:13                   ` Kenichi Handa
2002-10-25  5:36                     ` Richard Stallman [this message]
2002-10-23  9:57                   ` Paul Michael Reilly
2002-10-23 16:58                     ` Eli Zaretskii
2002-10-24  7:29                       ` Stefan Monnier
2002-10-24 17:30                         ` Eli Zaretskii
2002-10-21 15:33         ` Dave Love
2002-10-21 16:37           ` Kai Großjohann
2002-10-21 20:50             ` Stefan Monnier
2002-10-22  6:28               ` Kai Großjohann
2002-10-22  6:31         ` Kai Großjohann
2002-10-22 18:40           ` Eli Zaretskii
2002-10-23  5:24             ` Kai Großjohann
2002-10-16 12:21       ` Paul Michael Reilly
2002-10-19  4:56         ` Richard Stallman
2002-10-21 15:34       ` Dave Love
2002-10-22 16:36         ` Richard Stallman
2002-10-24 21:37           ` Dave Love
2002-10-16  4:38     ` Richard Stallman
2002-10-21 15:31       ` Dave Love

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E184x90-0003vI-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=pmr@pajato.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).