From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: MULE bites
Date: 19 Feb 1999 17:22:24 +0100 [thread overview]
Message-ID: <m3d836pdmn.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "16 Feb 1999 16:27:53 +0100"
Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> Okay, this is the first time I've been bitten by MULE (at least I
> presume that's where the error comes from). I nnoo'd a new backend,
> inheriting most of the stuff from nnmbox. I created a server for this
> backend. I added a message with a Latin-1 character. Now, when
> typing `g' in the group buffer, I get asked (two times, I've got two
> groups): Revisit file literally?
It's a bug somewhere in nnmbox, I think. Well, nnmbox probably fails
to grok some Mule stuff (like Vladimir said), and I have looked into
it some, but some fresh eyes would probably be very helpful. Could
you take a look at the problem as well?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-02-19 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-16 15:27 Kai.Grossjohann
1999-02-16 16:05 ` Vladimir Volovich
1999-02-19 16:22 ` Lars Magne Ingebrigtsen [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=m3d836pdmn.fsf@quimbies.gnus.org \
--to=larsi@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).