From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Quassia v0.22 failing on a coding type of 'raw-text
Date: 08 Jan 1998 20:07:20 +0100 [thread overview]
Message-ID: <kigk9cass2f.fsf@jagor.srce.hr> (raw)
In-Reply-To: Stephen Zander's message of "Thu, 08 Jan 1998 10:05:14 -0800"
Stephen Zander <srz@mckesson.com> writes:
> With much enthusiasm, I raced out & made the great leap from 5.4.22
> to the latest quassia release.
>
> However, gnus is now choking on the unknown coding system of 'raw-text
> during its startup.
>
> What did I miss?
It might be a good idea to provide a Lisp backtrace. Set
`debug-on-error' to t to get one.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Then... his face does a complete change of expression. It goes from
a "Vengeance is mine" expression, to a "What the fuck" blank look.
next prev parent reply other threads:[~1998-01-08 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-08 18:05 Stephen Zander
1998-01-08 19:07 ` Hrvoje Niksic [this message]
1998-01-09 16:30 ` 守岡 知彦 / MORIOKA Tomohiko
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=kigk9cass2f.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/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).