From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: mm-codepage-setup not quite right
Date: Fri, 28 Oct 2005 00:10:27 +0200 [thread overview]
Message-ID: <v9acgu392k.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <874q73olzt.fsf@zip.com.au>
On Thu, Oct 27 2005, Kevin Ryde wrote:
> I think the problem is that the call
>
> (mm-codepage-setup 1251 t)
>
> doesn't add windows-1251 to mm-charset-synonym-alist, the way the rest
> of the code expects. The test in mm-codepage-setup
>
> (mm-coding-system-p alias)
>
> looks dubious. I don't think the alias, in this case symbol
> windows-1251, will be known to coding-system-p.
Indeed. I don't remember why I added this test. I'll remove it.
> I noticed this when thinking to add some similar stuff myself, but
> cvs-up showed great minds think alike.
:-)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2005-10-27 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 0:13 Kevin Ryde
2005-10-27 22:10 ` Reiner Steib [this message]
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=v9acgu392k.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).