Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: [bugfixed] mm-charset-override-alist isn't used in decoding headers
Date: Fri, 12 Dec 2008 19:29:57 +0100	[thread overview]
Message-ID: <87myf1ckm2.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4m3agwe49m.fsf@jpl.org>

On Wed, Dec 10 2008, Katsumi Yamaoka wrote:

> (Note that that I mention here is the `gbk' charset, not the `gbk'
>  coding system.  So, `mm-charset-to-coding-system' is the best
>  choice for checking whether it is available or not.  However,
>  when loading mm-util,elc the default value section and/or the
>  `:set' section of `(defcustom mm-charset-override-alist ...)'
>  are processed before defining that function.)

Would it help to move the defcustom down (or the defun up)?  Or would
this introduce other problems?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2008-12-12 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 10:03 Katsumi Yamaoka
2008-12-12 18:29 ` Reiner Steib [this message]
2008-12-15  4:16   ` Katsumi Yamaoka

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=87myf1ckm2.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).