From: Alex Schroeder <alex@emacswiki.org>
Cc: Hiroshi Fujishima <pooh@nature.tsukuba.ac.jp>, ding@gnus.org
Subject: Re: spam.el: exiting groups is really really slow
Date: Tue, 02 Dec 2003 12:54:30 +0100 [thread overview]
Message-ID: <87ad6bsadl.fsf@emacswiki.org> (raw)
In-Reply-To: <4nptf8fe66.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Mon, 01 Dec 2003 15:58:41 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> Sorry. It's Alex Schroeder. Alex, let me know if you need more
> background, but basically it would be nice if spam-stat.el did a
> (let ((coding-system-for-write 'emacs-mule))) for (spam-stat-save).
I haven't been a diligent ding-reader lately, but the short summary
you're giving makes sense. Is emacs-mule really preferred?
In BBDB we're using the following, for example:
;; iso-2022-7bit should be OK (but not optimal for Emacs, at least --
;; emacs-mule would be better) with both Emacs 21 and XEmacs. Emacs
;; 22 will really need utf-8-emacs.
(defconst bbdb-file-coding-system (if (fboundp 'coding-system-p)
(if (coding-system-p 'utf-8-emacs)
'utf-8-emacs
'iso-2022-7bit))
"Coding system used for reading and writing `bbdb-file'.
This should not be changed by users.")
Alex.
--
.O. http://www.emacswiki.org/alex/
..O Schroeder's first law:
OOO The coffee at the office shall taste terrible.
next prev parent reply other threads:[~2003-12-02 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 22:37 David Z Maze
2003-11-25 22:58 ` Ted Zlatanov
2003-11-26 8:24 ` Danny Siu
[not found] ` <7coeuzzg6c.fsf@nature.tsukuba.ac.jp>
2003-11-26 15:41 ` Ted Zlatanov
2003-11-26 17:26 ` David Z Maze
2003-12-01 20:58 ` Ted Zlatanov
2003-12-02 11:54 ` Alex Schroeder [this message]
2003-12-02 18:34 ` Ted Zlatanov
[not found] ` <7ck75dzlfd.fsf@nature.tsukuba.ac.jp>
2003-12-03 23:40 ` Alex Schroeder
2003-12-10 23:07 ` Ted Zlatanov
2003-12-12 10:48 ` Alex Schroeder
2003-12-12 21:45 ` Ted Zlatanov
2003-11-26 20:34 ` Danny Siu
2003-11-26 20:33 ` Danny Siu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ad6bsadl.fsf@emacswiki.org \
--to=alex@emacswiki.org \
--cc=ding@gnus.org \
--cc=pooh@nature.tsukuba.ac.jp \
/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.
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 NNTP newsgroup(s).