GNU bug report logs - #4957
23.1.50; idlwave activated spuriously

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 4957 in the body.
You can then email your comments to 4957 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Richard Stallman <rms <at> gnu.org>
To: emacs-pretest-bug <at> gnu.org
Subject: 23.1.50; idlwave activated spuriously
Date: Wed, 18 Nov 2009 15:47:48 -0500

Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug <at> gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug.  If you can, give
a recipe starting from `emacs -Q':

I just did an update, my first since August,
and byte-recompile-file gave this output at the end:

    Loading system routine info in idle time...
    Failed to convert XML routine info, falling back on idlw-rinfo.
    Could not locate any system routine information.
    Loading system routine info in idle time...done
    Normalizing idlwave-system-routines in idle time...done
    Loading and normalizing library catalogs in idle time...done
    Finishing initialization in idle time...
    Scanning all buffers...

I suspect that some idlwave file does nontrivial actions
when it is merely loaded.

Message #10 received at 4957 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: rms <at> gnu.org
Cc: 4957 <at> debbugs.gnu.org
Subject: Re: bug#4957: 23.1.50; idlwave activated spuriously
Date: Tue, 24 Nov 2009 19:37:53 -0500

Richard Stallman wrote:

> I suspect that some idlwave file does nontrivial actions when it is
> merely loaded.

emacs -Q -l idlwave

does some work to set up the `idlwave-routines' variable. Is this an
issue? It doesn't change any aspect of Emacs behaviour, it's just
(verbosely) initializing so that it can start up faster when actually
needed.

It only starts doing it if Emacs is idle for
`idlwave-init-rinfo-when-idle-after' seconds (default 10). Change this
variable to 0 and it won't do anything until the information is
actually needed.

Message #15 received at 4957 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Richard Stallman <rms <at> gnu.org>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 4957 <at> debbugs.gnu.org
Subject: Re: bug#4957: 23.1.50; idlwave activated spuriously
Date: Thu, 26 Nov 2009 01:23:09 -0500

    does some work to set up the `idlwave-routines' variable. Is this an
    issue? It doesn't change any aspect of Emacs behaviour, it's just
    (verbosely) initializing so that it can start up faster when actually
    needed.

    It only starts doing it if Emacs is idle for
    `idlwave-init-rinfo-when-idle-after' seconds (default 10).

With that mechanism, this would not get activated during bootstrap,
right?  Either there is a bug in that code, or what I saw was
something else.

Do you see this when you bootstrap?

Message #18 received at 4957 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: rms <at> gnu.org
Cc: 4957 <at> debbugs.gnu.org
Subject: Re: bug#4957: 23.1.50; idlwave activated spuriously
Date: Mon, 30 Nov 2009 01:44:53 -0500

Richard Stallman wrote:

> With that mechanism, this would not get activated during bootstrap,
> right?  Either there is a bug in that code, or what I saw was
> something else.
>
> Do you see this when you bootstrap?

No I don't, because bootstrapping starts a new Emacs instance to
compile every file in a pure environment. They exit when done, so
never hang around for 10 seconds of idle time to allow this code to
run. I thought you said you did a recompile, which is different and
compiles everything in a single Emacs instance.

Message #23 received at 4957 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Richard Stallman <rms <at> gnu.org>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 4957 <at> debbugs.gnu.org
Subject: Re: bug#4957: 23.1.50; idlwave activated spuriously
Date: Mon, 30 Nov 2009 23:10:03 -0500

    No I don't, because bootstrapping starts a new Emacs instance to
    compile every file in a pure environment. They exit when done, so
    never hang around for 10 seconds of idle time to allow this code to
    run. I thought you said you did a recompile, which is different and
    compiles everything in a single Emacs instance.

I think this occurred during a bootstrap.  But I can't be sure
of that memory after the time that has gone by.

Message #28 received at 4957 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: rms <at> gnu.org
Cc: 4957 <at> debbugs.gnu.org
Subject: Re: bug#4957: 23.1.50; idlwave activated spuriously
Date: Tue, 01 Dec 2009 22:08:04 -0500

Richard Stallman wrote:

> I think this occurred during a bootstrap.  But I can't be sure
> of that memory after the time that has gone by.

I can't see how it could happen during bootstrap, and have never seen
it myself. I do see how it could happen with `make recompile' or
something similar.

Message #33 received at 4957-done <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: 4957-done <at> debbugs.gnu.org
Subject: Re: bug#4957: 23.1.50; idlwave activated spuriously
Date: Sat, 09 Jul 2011 21:10:04 -0400

I'm closing this report. I think the details at

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=4957

basically explain that there is nothing to do here.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.