From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: MULE bites
Date: 16 Feb 1999 16:27:53 +0100 [thread overview]
Message-ID: <vafk8xiid1i.fsf@ramses.cs.uni-dortmund.de> (raw)
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?
When I say yes, I get that dreaded \201 thingy.
What do I do now?
kai
--
I like _\bb_\bo_\bt_\bh kinds of music.
next reply other threads:[~1999-02-16 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-16 15:27 Kai.Grossjohann [this message]
1999-02-16 16:05 ` Vladimir Volovich
1999-02-19 16:22 ` Lars Magne Ingebrigtsen
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=vafk8xiid1i.fsf@ramses.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).