Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Lost rfc2047 decoding in the summary buffer (test æøå)
Date: Thu, 28 Dec 2006 16:35:17 +0100	[thread overview]
Message-ID: <v9d564kp8q.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <8764bwkred.fsf@bang.priv.no>

On Thu, Dec 28 2006, Steinar Bang wrote:

>>>>>> Reiner Steib <reinersteib+gmane@imap.cc>:
>
>> I cannot reproduce this with Emacs 21. 
>
> In other words: this article shows "(test æøå)", instead of "(test
> =?iso-8859-1?Q?=E6=F8=E5=29?=" at the end of the subject in the
> summary buffer?

Yes.

>> Could you try to reproduce with a minimal Gnus setup and/or check
>> for any relevant customizations?
>
> Hm... how do I create a minimal Gnus setup, without messing up my
> current setup?  Create a different user account?

That's option 1.  Option 2 is to create a new home directory for this
Emacs session:

--8<---------------cut here---------------start------------->8---
emacs_test=~/path/to/my/emacs_test
mkdir -p $emacs_test
cd $emacs_test
ln -s ~/.Xauthority .
HOME=$PWD emacs &
--8<---------------cut here---------------end--------------->8---

The .emacs and .gnus.el files in $emacs_test should only contain
minimal settings (e.g. `load-path' for Gnus, `gnus-select-method').

Option 3 is to set `gnus-home-directory' to the value of $emacs_test
within Emacs before loading ~/.gnus.el or maybe better start from
"emacs -q".

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




  reply	other threads:[~2006-12-28 15:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28  7:18 Steinar Bang
2006-12-28  7:51 ` Steinar Bang
2006-12-28  8:42   ` Reiner Steib
2006-12-28 14:48     ` Steinar Bang
2006-12-28 15:35       ` Reiner Steib [this message]
2006-12-30 11:04         ` Steinar Bang
2006-12-30 12:16           ` Reiner Steib
2006-12-30 12:37             ` Steinar Bang
2006-12-30 13:27               ` Steinar Bang

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=v9d564kp8q.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).