From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Problem with latest snapshot
Date: 17 Dec 2000 10:36:26 -0500 [thread overview]
Message-ID: <2nae9v6ow5.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <x0r937fc7f.fsf@visiontech-dml.com>
Gregory Chernov <greg@visiontech-dml.com> writes:
> Hi,
>
> I've found couple of problems with latest snapshot
> (gnus-CURRENT-20001217).
>
> 1. Symbol's function definition is void: charsetp
> I'm using xemacs without mule and charsetp function is not defined.
> For now I can live with simple workaround:
> (defun charsetp (&optional var) nil)
Fixed. But I am wondering whether set-buffer-multibyte is defined in
XEmacs w/o mule.
> 2. Strange problem with gnus-mime-save-part-and-strip.
> I used this function on some message with gif image
> and everything worked OK. Problems started when I
> tried to look on the results.
Fixed.
ShengHuo
next prev parent reply other threads:[~2000-12-17 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-17 12:45 Gregory Chernov
2000-12-17 15:36 ` ShengHuo ZHU [this message]
2000-12-17 17:45 ` Björn Torkelsson
2000-12-19 10:36 ` Didier Verna
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=2nae9v6ow5.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).