From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: Gnus 5.8.2: group list
Date: 06 Dec 1999 13:38:16 -0500 [thread overview]
Message-ID: <oq4sdvvrs7.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Jaap-Henk Hoepman's message of "06 Dec 1999 09:54:18 +0100"
Jaap-Henk Hoepman <hoepman@cs.utwente.nl> writes:
> > Jack> This is where things get funny. If I do a new 'l', then a
> > Jack> /different/ group will show up as a duplicate.
> >
> > I saw similar behaviour in PGnus 0.97 and PGnus 0.98.
I'm seeing this too for a good while, but it only affects an experimental
group with diacriticic characters in its name, everything else is fine.
I should probably have reported it, if I knew I had more time to experiment
about such groups, but I'm lacking time in these weeks.
P.S. - I also received an UTF-8 encoded message which was also Base64
coded, and experimented Mule problems (spurious \200). Same situation:
such things require time just to begin to understand, at least enough to
sustain a conversation with Lars about it :-).
--
François Pinard http://www.iro.umontreal.ca/~pinard
prev parent reply other threads:[~1999-12-06 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-05 5:50 Jack Vinson
1999-12-06 0:43 ` Brian May
1999-12-06 8:54 ` Jaap-Henk Hoepman
1999-12-06 18:38 ` François Pinard [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=oq4sdvvrs7.fsf@titan.progiciels-bpi.ca \
--to=pinard@iro.umontreal.ca \
--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).