message in *Compile Log* buffer

[Sebastian Luque]

Thanks to Ralf Angeli for replying to this message, which I'm resending
through auctex's bug reporting function, as per his request.

Since upgrading to auctex 11.54, I receive the following message in the
*Compile Log* buffer:

** reference to free variable minor-mode-list

whenever I open some of my LaTeX files. I'm affraid that as the message
appears when these files are opened, I cannot identify which lines in the
files are causing the message to pop up.

Sebastian


Emacs : GNU Emacs 21.3.1 (i386-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2004-10-16 on raven, modified by Debian
Package: AUCTeX 11.54

current state:
==============
(setq
window-system 'x
LaTeX-version "2e"
TeX-style-path '("style/" "auto/" "/usr/share/emacs21/site-lisp/auctex/style/"
"/var/lib/auctex/emacs21/"
"/usr/local/share/emacs/site-lisp/auctex/style/")
TeX-auto-save nil
TeX-parse-self nil
TeX-master t
)

[Frank Küster]

Post by Sebastian Luque
Thanks to Ralf Angeli for replying to this message, which I'm resending
through auctex's bug reporting function, as per his request.
Since upgrading to auctex 11.54, I receive the following message in the
** reference to free variable minor-mode-list
whenever I open *some* of my LaTeX files.

Does that mean it doesn't occur all the time, but only with certain
files? Would it be possible to make one of them publically available?

Post by Sebastian Luque
Emacs : GNU Emacs 21.3.1 (i386-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2004-10-16 on raven, modified by Debian
Package: AUCTeX 11.54

Same here for me (except for the date and raven, I have an older
backport), but I never got the message.

Regards, Frank

[David Kastrup]

Post by Frank Küster

Post by Sebastian Luque
Thanks to Ralf Angeli for replying to this message, which I'm
resending through auctex's bug reporting function, as per his
request.
Since upgrading to auctex 11.54, I receive the following message in the
** reference to free variable minor-mode-list
whenever I open *some* of my LaTeX files.

Does that mean it doesn't occur all the time, but only with certain
files? Would it be possible to make one of them publically available?

Post by Sebastian Luque
Emacs : GNU Emacs 21.3.1 (i386-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2004-10-16 on raven, modified by Debian
Package: AUCTeX 11.54

Same here for me (except for the date and raven, I have an older
backport), but I never got the message.

Something like this might possibly happen if you are byte-compiling
with a different Emacs version than you are using for running AUCTeX.

[Sebastian Luque]

Post by Frank Küster
Does that mean it doesn't occur all the time, but only with certain
files? Would it be possible to make one of them publically available?

I just looked into this a bit deeper and it's actually happening with all
files, but the *Compile Log* buffer is popping up only the first time I open
a LaTeX file in an Emacs session. The buffer does pop up when opening any
LaTeX file, if it's the first one in the current Emacs session. Thank you.

[Ralf Angeli]

Post by Sebastian Luque

Post by Frank Küster
Does that mean it doesn't occur all the time, but only with certain
files? Would it be possible to make one of them publically available?

I just looked into this a bit deeper and it's actually happening with all
files, but the *Compile Log* buffer is popping up only the first time I open
a LaTeX file in an Emacs session. The buffer does pop up when opening any
LaTeX file, if it's the first one in the current Emacs session. Thank you.

That means it happens as soon as tex.el(c) is being loaded and the
advice is being applied.

Unless somebody is able to debug this problem (I can't because I
cannot reproduce the behavior) it doesn't make sense to invest more
time in it. With the change I made in CVS the *Compile Log* should
not pop up anymore.

[David Kastrup]

Post by Ralf Angeli

Post by Sebastian Luque

Post by Frank Küster
Does that mean it doesn't occur all the time, but only with certain
files? Would it be possible to make one of them publically available?

I just looked into this a bit deeper and it's actually happening with all
files, but the *Compile Log* buffer is popping up only the first time I open
a LaTeX file in an Emacs session. The buffer does pop up when opening any
LaTeX file, if it's the first one in the current Emacs session. Thank you.

That means it happens as soon as tex.el(c) is being loaded and the
advice is being applied.
Unless somebody is able to debug this problem (I can't because I
cannot reproduce the behavior) it doesn't make sense to invest more
time in it. With the change I made in CVS the *Compile Log* should
not pop up anymore.

define-minor-mode is a Lisp macro in `easy-mmode'.

That means that we need something like
(eval-when-compile (require 'easy-mmode))

so that the macro is available at compile time.

Remind me: what kind of code depended on it?

[Ralf Angeli]

Post by David Kastrup

Post by Ralf Angeli
That means it happens as soon as tex.el(c) is being loaded and the
advice is being applied.
Unless somebody is able to debug this problem (I can't because I
cannot reproduce the behavior) it doesn't make sense to invest more
time in it. With the change I made in CVS the *Compile Log* should
not pop up anymore.

define-minor-mode is a Lisp macro in `easy-mmode'.
That means that we need something like
(eval-when-compile (require 'easy-mmode))
so that the macro is available at compile time.
Remind me: what kind of code depended on it?

I'm sorry, I don't know what you mean.

The problem is `minor-mode-list'. And this variable is only present
in CVS Emacs, not in Emacs 21.3 and earlier and not in XEmacs. I
thought that checking for `(boundp 'minor-mode-list)' would suffice to
silence the byte compiler, but in some cases obviously it isn't.

[David Kastrup]

Post by Ralf Angeli

Post by David Kastrup
define-minor-mode is a Lisp macro in `easy-mmode'.
That means that we need something like
(eval-when-compile (require 'easy-mmode))
so that the macro is available at compile time.
Remind me: what kind of code depended on it?

I'm sorry, I don't know what you mean.

I'm probably confusing this with a different bug report.

Post by Ralf Angeli
The problem is `minor-mode-list'. And this variable is only present
in CVS Emacs, not in Emacs 21.3 and earlier and not in XEmacs. I
thought that checking for `(boundp 'minor-mode-list)' would suffice
to silence the byte compiler, but in some cases obviously it isn't.

Well, in recent versions of Emacs CVS, it should be sufficient. But
it is not the recent versions that are missing minor-mode-list.

What you can do is just

(defvar minor-mode-list)

at the top of the file. That has no side effects except for silencing
the byte compiler.

[Ralf Angeli]

Post by David Kastrup

Post by Ralf Angeli
The problem is `minor-mode-list'. And this variable is only present
in CVS Emacs, not in Emacs 21.3 and earlier and not in XEmacs. I
thought that checking for `(boundp 'minor-mode-list)' would suffice
to silence the byte compiler, but in some cases obviously it isn't.

Well, in recent versions of Emacs CVS, it should be sufficient. But
it is not the recent versions that are missing minor-mode-list.
What you can do is just
(defvar minor-mode-list)
at the top of the file. That has no side effects except for silencing
the byte compiler.

Okay, thanks for the hint. But I think I'll just leave the code
as-is. I don't think the number and definition of minor modes will
change frequently and thus maintenance of a list of minor modes in the
advice will rarely be needed. In addition I am not really sure about
the security implications of calling minor mode functions. With an
explicit list we are a bit more conservative compared to a match with
a regular expression.

[Benno Overeinder]

Post by Sebastian Luque

Post by Frank Küster
Does that mean it doesn't occur all the time, but only with certain
files? Would it be possible to make one of them publically available?

I just looked into this a bit deeper and it's actually happening with all
files, but the *Compile Log* buffer is popping up only the first time I open
a LaTeX file in an Emacs session. The buffer does pop up when opening any
LaTeX file, if it's the first one in the current Emacs session. Thank you.

Same message in *Compile Log* appears on my machine (running Debian 3.1
(sarge)). The buffer is popping up only the first time I open a LaTeX file in
an Emacs session.

Regards,

-- Benno

[Benno Overeinder]

Post by Benno Overeinder

Post by Sebastian Luque

Post by Frank Küster
Does that mean it doesn't occur all the time, but only with certain
files? Would it be possible to make one of them publically available?

I just looked into this a bit deeper and it's actually happening with all
files, but the *Compile Log* buffer is popping up only the first time I open
a LaTeX file in an Emacs session. The buffer does pop up when opening any
LaTeX file, if it's the first one in the current Emacs session. Thank you.

Same message in *Compile Log* appears on my machine (running Debian 3.1
(sarge)). The buffer is popping up only the first time I open a LaTeX file in
an Emacs session.

A follow-up on a message of my own...

I use also planner mode (in combination with emacs-wiki), and if I remove the
(require 'planner) and (require 'emacs-wiki) from my .emacs, the message does
_not_ appear in *Compile Log*.

So it seams that auctex and planner bite each other in some way.

Regards,

-- Benno