Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: today's CVS Gnus: message.el problem
Date: Fri, 13 Jun 2003 10:45:40 -0400	[thread overview]
Message-ID: <4ny906ave3.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <rzqk7br7wvs.fsf@albion.dl.ac.uk> (Dave Love's message of "Thu, 12 Jun 2003 23:29:27 +0100")

On Thu, 12 Jun 2003, d.love@dl.ac.uk wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>> While compiling the end of the data in file
>> /home/tzz/gnus/gnus/lisp/message.el: ** The function
>> `delete-extent' is not known to be defined.
> 
> Assuming you're talking about Emacs, why is that a problem?  (For
> what it's worth, you won't get a warning with the development
> version of the compiler.)

I didn't know if this was a problem.  I get the same error if I forget
to define a function, and I did not notice the featurep 'xemacs right
above the use of delete-extent.

Ted



      reply	other threads:[~2003-06-13 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 20:55 Ted Zlatanov
2003-06-12 22:29 ` Dave Love
2003-06-13 14:45   ` Ted Zlatanov [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=4ny906ave3.fsf@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /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).