From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: gnus-picon.el has a wart or two this morning
Date: Sat, 29 Dec 2001 15:41:45 -0500 [thread overview]
Message-ID: <2nitap7o8m.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <vxkelleqefi.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Sat, 29 Dec 2001 09:38:41 -0500")
Karl Kleinpaste <karl@charcoal.com> writes:
> As of "cvs update" 5 minutes ago:
>
> Compiling /home/karl/Emacs/gnus/lisp/gnus-picon.el...
> While compiling gnus-picons-make-annotation in file /home/karl/Emacs/gnus/lisp/gnus-picon.el:
> ** function gnus-picons-make-annotation defined multiple times in this file
> While compiling the end of the data:
> ** The following functions are not known to be defined:
> set-annotation-data, set-annotation-action, annotation-glyph,
> set-annotation-glyph
> Wrote /home/karl/Emacs/gnus/lisp/gnus-picon.elc
This wart is covered, sort of.
ShengHuo
prev parent reply other threads:[~2001-12-29 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 14:38 Karl Kleinpaste
2001-12-29 20:41 ` ShengHuo ZHU [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=2nitap7o8m.fsf@zsh.cs.rochester.edu \
--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).