From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: customizing mm-charset-synonym-alist (was: nail uses iso8859-1 instead of iso-8859-1)
Date: Thu, 26 Apr 2007 21:44:39 +0200 [thread overview]
Message-ID: <v98xce2a54.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mslaouk8p.fsf@jpl.org>
On Thu, Apr 26 2007, Katsumi Yamaoka wrote:
> I've also made it use defcustom, so you can now customize the alist
> easily.
I think this is not a good idea.
1. `mm-charset-synonym-alist' is modified by mm-setup-codepage-*, so a
user will see "CHANGED outside Customize; operating on it here may be
unreliable."
,----
| ;; Initialize:
| (mm-setup-codepage-iso-8859)
| (mm-setup-codepage-ibm)
`----
2. The initial value depends on the availability of charsets (lots of
`mm-coding-system-p's). So it will change when using different
Emacs versions and flavors. But if the user has customized it,
this conditionals are eliminated.
IMHO, if we want a customizable variable, we should create a new
variable (default: nil) and construct `mm-charset-synonym-alist' from
the new one, `mm-codepage-iso-8859-list' and `mm-codepage-ibm-list'
(using mm-setup-codepage-*). A new setup function should check if the
cdr of each element is a valid charset and add it to
`mm-charset-synonym-alist'.
BTW, if former defvars are changed to defcustoms, the :version is the
one when it's made customizable, not when the defvar was introduced.
So ":version "21.1" is not correct.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-04-26 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 15:44 nail uses iso8859-1 instead of iso-8859-1 NAKAJI Hiroyuki
2007-04-25 23:06 ` Katsumi Yamaoka
2007-04-26 19:44 ` Reiner Steib [this message]
2007-04-26 22:42 ` customizing mm-charset-synonym-alist Katsumi Yamaoka
2007-05-01 16:01 ` nail uses iso8859-1 instead of iso-8859-1 Reiner Steib
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=v98xce2a54.fsf_-_@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
/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).