* bug#4957: 23.1.50; idlwave activated spuriously
@ 2009-11-18 20:47 Richard Stallman
2009-11-25 0:37 ` Glenn Morris
0 siblings, 1 reply; 7+ messages in thread
From: Richard Stallman @ 2009-11-18 20:47 UTC (permalink / raw)
To: emacs-pretest-bug
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@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.
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#4957: 23.1.50; idlwave activated spuriously
2009-11-18 20:47 bug#4957: 23.1.50; idlwave activated spuriously Richard Stallman
@ 2009-11-25 0:37 ` Glenn Morris
2009-11-26 6:23 ` Richard Stallman
0 siblings, 1 reply; 7+ messages in thread
From: Glenn Morris @ 2009-11-25 0:37 UTC (permalink / raw)
To: rms; +Cc: 4957
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.
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#4957: 23.1.50; idlwave activated spuriously
2009-11-25 0:37 ` Glenn Morris
@ 2009-11-26 6:23 ` Richard Stallman
2009-11-30 6:44 ` Glenn Morris
0 siblings, 1 reply; 7+ messages in thread
From: Richard Stallman @ 2009-11-26 6:23 UTC (permalink / raw)
To: Glenn Morris; +Cc: 4957
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?
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#4957: 23.1.50; idlwave activated spuriously
2009-11-26 6:23 ` Richard Stallman
@ 2009-11-30 6:44 ` Glenn Morris
2009-12-01 4:10 ` Richard Stallman
0 siblings, 1 reply; 7+ messages in thread
From: Glenn Morris @ 2009-11-30 6:44 UTC (permalink / raw)
To: rms; +Cc: 4957
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.
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#4957: 23.1.50; idlwave activated spuriously
2009-11-30 6:44 ` Glenn Morris
@ 2009-12-01 4:10 ` Richard Stallman
2009-12-02 3:08 ` Glenn Morris
0 siblings, 1 reply; 7+ messages in thread
From: Richard Stallman @ 2009-12-01 4:10 UTC (permalink / raw)
To: Glenn Morris; +Cc: 4957
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.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-07-10 1:10 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-18 20:47 bug#4957: 23.1.50; idlwave activated spuriously Richard Stallman
2009-11-25 0:37 ` Glenn Morris
2009-11-26 6:23 ` Richard Stallman
2009-11-30 6:44 ` Glenn Morris
2009-12-01 4:10 ` Richard Stallman
2009-12-02 3:08 ` Glenn Morris
2011-07-10 1:10 ` Glenn Morris
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.