From: Austin Clements <amdragon@MIT.EDU>
To: Jameson Graef Rollins <jrollins@finestructure.net>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Fix "not defined at runtime" warning
Date: Thu, 9 Aug 2012 10:13:46 -0400 [thread overview]
Message-ID: <20120809141346.GH11179@mit.edu> (raw)
In-Reply-To: <87628sa4a8.fsf@servo.finestructure.net>
Quoth Jameson Graef Rollins on Aug 09 at 12:54 am:
> On Wed, Aug 08 2012, Austin Clements <amdragon@MIT.EDU> wrote:
> > Previously, the Emacs byte compiler produced the warning
> >
> > the function `remove-if-not' might not be defined at runtime.
> >
> > because we only required cl at compile-time (not runtime). This fixes
> > this warning by requiring cl at runtime, ensuring that the definition
> > of remove-if-not is available.
> > ---
> > emacs/notmuch-lib.el | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/emacs/notmuch-lib.el b/emacs/notmuch-lib.el
> > index 30db58f..900235b 100644
> > --- a/emacs/notmuch-lib.el
> > +++ b/emacs/notmuch-lib.el
> > @@ -24,7 +24,7 @@
> > (require 'mm-view)
> > (require 'mm-decode)
> > (require 'json)
> > -(eval-when-compile (require 'cl))
> > +(require 'cl)
> >
> > (defvar notmuch-command "notmuch"
> > "Command to run the notmuch binary.")
>
> LGTM. I think it would be good to finally just give in a require cl, so
> we can finally put to rest the long standing schizophrenia we've had in
> regards to using it, and maybe finally kill the compile warnings that
> keep popping up.
I think we already gave in [0], we just weren't very thorough about
it.
[0] id:"m262g864dz.fsf@wal122.wireless-pennnet.upenn.edu"
next prev parent reply other threads:[~2012-08-09 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 21:40 [PATCH] emacs: Fix "not defined at runtime" warning Austin Clements
2012-08-09 7:46 ` Tomi Ollila
2012-08-09 14:12 ` Austin Clements
2012-08-09 7:54 ` Jameson Graef Rollins
2012-08-09 14:13 ` Austin Clements [this message]
2012-08-12 19:49 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120809141346.GH11179@mit.edu \
--to=amdragon@mit.edu \
--cc=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).