From: nexus@panix.com (Jeff Berry)
Subject: Re: idlwave won't byte compile
Date: 7 Sep 2004 08:08:08 -0400 [thread overview]
Message-ID: <chk8b8$pca$1@panix5.panix.com> (raw)
In-Reply-To: 4138ACC3.7020000@yahoo.com
In article <4138ACC3.7020000@yahoo.com>,
Kevin Rodgers <ihs_4664@yahoo.com> wrote:
>Jeff Berry wrote:
> > I'm trying to install idlwave-5.3 for a user at my site, and it
> > won't byte compile. I'm running AIX4.3 and emacs-21.3, and when
> > I try to make idlwave, I get this:
> > Am I, not being a lisp programmer or much of emacs user, missing something
> > obvious here?
>No, idlwave's author did: idlwave.el and idlw-shell.el must have
>(require 'idlw-help), but idlw-help.el does not have (provide 'idlw-help);
>so add it at the end of the file.
>Kevin Rodgers
Thanks very much. That was pretty much it. I actually had to add two
lines:
(provide 'idlw-help)
(provide 'idlwave-help)
But once I knew what I was looking for, it was easy to sort out.
Thanks again,
Jeff Berry/NASA GISS
prev parent reply other threads:[~2004-09-07 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 13:54 idlwave won't byte compile Jeff Berry
2004-09-03 17:41 ` Kevin Rodgers
2004-09-07 12:08 ` Jeff Berry [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
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='chk8b8$pca$1@panix5.panix.com' \
--to=nexus@panix.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.
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).