unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 11847@debbugs.gnu.org
Subject: bug#11847: 24.1.50; Error: Don't know how to compile #[nil "..."]
Date: Thu, 05 Jul 2012 12:14:09 -0400	[thread overview]
Message-ID: <jwvhatmkwxq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <A94A4AB880B54D2495990A02841903F6@us.oracle.com> (Drew Adams's message of "Thu, 5 Jul 2012 08:49:22 -0700")

> ping. 

AFAIK your problem should be fixed in trunk now.


        Stefan


>> I guess the bug has to do with why it thinks it cannot do its 
>> job here.  Unless there is some bug in my code that makes
>> compilation impossible where it should otherwise be possible.
>> Can you tell by looking at the code I sent?  Or do you
>> think there is a byte-compiler bug here?

> There was a similar bug report (#11837), which was closed after finding a
> font-latex bug.  I don't know how to proceed with this bug.  I sent the
> backtrace you requested.

> One thing I wonder about, which might be pertinent here:

> Function `icicle-cmd2-after-load-bookmark+' is invoked after Bookmark+ is
> loaded:

> (eval-after-load "bookmark+" '(icicle-cmd2-after-load-bookmark+))

> That function does this:

> (icicle-define-file-command 'icicle-bookmark-a-file...)

> And `icicle-define-file-command' is a macro that is not available at runtime.
> It was available at byte-compile time, so I was thinking that it would be
> expanded in the body of `icicle-cmd2-after-load-bookmark+', and things would be
> OK.

> (And things did work OK before the Emacs 24 build of this bug report, since the
> byte-compiler ignored some errors that apparently did not cause a problem for
> this code.)

> It is `icicle-cmd2-after-load-bookmark+' that tries to byte-compile
> `icicle-bookmark-a-file' after defining it.

> Does this info help?  I want to avoid loading the file of macros at runtime.
> And I want to avoid defining `icicle-bookmark-a-file' and other bookmark
> commands unless Bookmark+ is loaded.

> Please advise.  Thx.





  reply	other threads:[~2012-07-05 16:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  3:28 bug#11847: 24.1.50; Error: Don't know how to compile #[nil "..."] Drew Adams
2012-07-03  6:12 ` Drew Adams
2012-07-03  6:21   ` Drew Adams
2012-07-03 13:42 ` Stefan Monnier
2012-07-03 14:44   ` Drew Adams
2012-07-03 17:26     ` Stefan Monnier
2012-07-03 18:00       ` Drew Adams
2012-07-05 15:49         ` Drew Adams
2012-07-05 16:14           ` Stefan Monnier [this message]
2012-07-05 16:20             ` Drew Adams
2012-07-17  5:56               ` Drew Adams
2012-07-17  5:50         ` Drew Adams
2012-07-17  6:37           ` Stefan Monnier
2012-07-17  6:40             ` Drew Adams

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=jwvhatmkwxq.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=11847@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).