unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: nyc4bos@aol.com
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10034@debbugs.gnu.org
Subject: bug#10034: 24.0.91; max-specpdl-size error
Date: Sat, 19 Nov 2011 00:32:05 -0500	[thread overview]
Message-ID: <84pqgosmne.fsf@aol.com> (raw)
In-Reply-To: <83wrb0d8ax.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 16 Nov 2011 06:01:58 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: nyc4bos@aol.com
>> Date: Tue, 15 Nov 2011 22:43:13 -0500
>> Cc: 10034@debbugs.gnu.org
>> 
>> > Please first try to:
>> >
>> >  rm lisp/window.elc; make
>> >
>> > just to make sure you're not seeing the recent "rebuild" problem.
>> 
>> I'm using the pre-built Emacs Windows build and don't have the
>> make utilities on this machine.
>> 
>> Presumably, this will suffice:
>> 
>>     emacs -batch -f batch-byte-compile lisp/window.el
>
> No, it will not.  window.elc is preloaded into the emacs.exe binary
> you have.  If you recompile window.el as above, it will not be used,
> unless you manually load it into Emacs:
>
>   M-x load-library RET window RET
>
> And then it will be used, but as soon as you restart Emacs, you will
> have to reload it again, or be left with the old version.

Thanks for the information.

I have a couple of questions about this:

1. Is there any way to determine that the .elc file that I have
   on-disk matches the preloaded .elc in the emacs.exe binary?

   Since I use the pre-built Emacs binary when on Windows, I presume
   that the .elc files I have on-disk were the ones loaded in the binary
   but I have no way of truely knowing unless I can query Emacs to tell
   me.

2. What are the preloaded .elc files?  Are they the ones from loadup.el?

   Can one ask the Emacs instance to compare the .elc file on-disk with
   the one that it was preloaded with to verify they are the same?

3. Can you startup Emacs to either ignore its (non-necessary) preloaded
   .elc files if the same file name (.el/.elc) resides on-disk or
   tell it to only use the files (.el/.elc) in the `load-path'
   and not what was preloaded?

Thanks.







  reply	other threads:[~2011-11-19  5:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13  4:46 bug#10034: 24.0.91; max-specpdl-size error nyc4bos
2011-11-13 10:49 ` martin rudalics
2011-11-13 23:01   ` nyc4bos
2011-11-14  8:54     ` martin rudalics
2011-11-14 14:38       ` Drew Adams
2011-11-16  2:59       ` nyc4bos
2011-11-14  1:24   ` nyc4bos
2011-11-14  8:54     ` martin rudalics
2011-11-16  3:14       ` nyc4bos
2011-11-16  3:43   ` nyc4bos
2011-11-16  4:01     ` Eli Zaretskii
2011-11-19  5:32       ` nyc4bos [this message]
2011-11-19  8:12         ` Eli Zaretskii
2011-12-09 23:48   ` bug#7658: 24.0.50; emacsclient not raising frame nyc4bos
2011-11-14 14:08 ` bug#10034: 24.0.91; max-specpdl-size error Stefan Monnier

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=84pqgosmne.fsf@aol.com \
    --to=nyc4bos@aol.com \
    --cc=10034@debbugs.gnu.org \
    --cc=eliz@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.
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).