Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: New agent code
Date: Mon, 25 Nov 2002 08:25:00 +0100	[thread overview]
Message-ID: <84wun2un5f.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <yotly97i1eya.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> While compiling latest Gnus using XEmacs, the byte-compiler
> complains as follows:
>
> While compiling gnus-agent-check-overview-buffer in file /Work/gnus/lisp/gnus-agent.el:
>   ** reference to free variable deactivate-mark
> While compiling the end of the data:
>   ** the function number-at-point is not known to be defined.

It seems all these are in gnus-agent-check-overview-buffer.  This
function is intended to function as a sanity check until more testing
determines that everything works correctly.

Under these circumstances, maybe it is okay to require FSF compat
code?

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)



  reply	other threads:[~2002-11-25  7:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25  2:13 Henrik Enberg
2002-11-25  2:42 ` Henrik Enberg
2002-11-25  3:12   ` Henrik Enberg
2002-11-25  7:31     ` Kai Großjohann
2002-11-26  3:17       ` Kevin Greiner
2002-11-26  7:30         ` Kai Großjohann
2002-11-27 10:47           ` Denis Yakovlev
2002-11-27 17:52             ` Kevin Greiner
2002-11-27 19:46               ` Denis Yakovlev
2002-11-27 21:29               ` Kai Großjohann
2002-11-28  5:51                 ` Kevin Greiner
2002-11-28 18:24                   ` Denis Yakovlev
2002-11-25  3:54 ` Katsumi Yamaoka
2002-11-25  7:25   ` Kai Großjohann [this message]
2002-11-25 20:11     ` David S Goldberg
2002-11-25 20:32       ` Kai Großjohann
2002-11-26 14:43         ` David S Goldberg
2002-11-26 15:11           ` Kai Großjohann
2002-12-03 14:18             ` David S Goldberg
2002-11-25  7:30 ` Kai Großjohann
2002-11-25 16:58   ` Henrik Enberg
2002-11-25 20:17     ` Kai Großjohann

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=84wun2un5f.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@uni-duisburg.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).