all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: nero.el requires emacs-21.X
Date: Wed, 13 Apr 2005 09:59:06 -0600	[thread overview]
Message-ID: <d3jfeb$jep$1@sea.gmane.org> (raw)
In-Reply-To: <E1DLUTr-0007nX-00@lab45.ma.utexas.edu>

Joe Corneli wrote:
 > 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

I just loaded a more recent version of nero.el in Emacs 21.3 (invoked
with -q) and ran M-x nero-home with no errors:

;; Time-stamp: <jac -- Sun Apr  3 16:28:44 CDT 2005>

Furthermore, I don't see any references to macro-declaration-function in
nero.el.  So the bug report itself is a little suspicious...

 >    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

-- 
Kevin Rodgers

      reply	other threads:[~2005-04-13 15:59 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 ` nero.el requires emacs-21.X Joe Corneli
2005-04-13 15:59   ` Kevin Rodgers [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='d3jfeb$jep$1@sea.gmane.org' \
    --to=ihs_4664@yahoo.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.