From: Joe Corneli <jcorneli@math.utexas.edu>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: nero.el requires emacs-21.X
Date: Tue, 12 Apr 2005 18:07:39 -0500 [thread overview]
Message-ID: <E1DLUTr-0007nX-00@lab45.ma.utexas.edu> (raw)
In-Reply-To: <16988.21013.317619.9402@chlr4920.ch.intel.com> (ascott@sedona.ch.intel.com)
Hm... I use CVS, so um, yeah. Never ran into that.
If your emacs is pre March 2002, its pretty old (like, older than my
entire Emacs Lisp coding life).
Should I make changes to support these old Emacses - and if so, anyone
have any advice about what to do? I haven't done anything that seems
very out of the ordinary (to me)... I can dig around - but maybe this
issue is familiar to people who lived through the changes you're
talking about, in the flesh.
Joe,
I happened to try to load nero.el in Emacs-21.3 today; it fails
with
;;; nero.el --- a fast Lynx-based browser for Emacs
;; Copyright (C) 2005 Joe Corneli <jcorneli@math.utexas.edu>
;; Time-stamp: <jac -- Mon Mar 28 00:36:43 CST 2005>
Loading nero...
load: Symbol's value as variable is void: macro-declaration-function
Examining the CVS lisp/Changelogs, this is because
macro-declaration-function didn't exist until March 2002.
You might want some sort of test like
(if (fboundp 'macro-declaration-function) ...)
somewhere, etc.
2002-03-24 Gerd Moellmann <gerd@gnu.org>
* subr.el (macro-declaration-function): New function. Set the
variable macro-declaration-function to it.
now in lisp/byte-run.el
2005-03-14 Lute Kamstra <lute@gnu.org>
* emacs-lisp/debug.el (debugger-make-xrefs): Docstring fix.
Ignore a `*' at the beginning of a line.
* subr.el (macro-declaration-function): Move to emacs-lisp/byte-run.el.
Cheers,
Andy Scott
next parent reply other threads:[~2005-04-12 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16988.21013.317619.9402@chlr4920.ch.intel.com>
2005-04-12 23:07 ` Joe Corneli [this message]
2005-04-13 15:59 ` nero.el requires emacs-21.X Kevin Rodgers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1DLUTr-0007nX-00@lab45.ma.utexas.edu \
--to=jcorneli@math.utexas.edu \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).