unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Neil Jackson <neil.jackson@live.ca>, 16573@debbugs.gnu.org
Subject: bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile
Date: Tue, 28 Jan 2014 09:14:14 +0100	[thread overview]
Message-ID: <87k3dkttex.fsf__27231.9985939705$1390896945$gmane$org@gnu.org> (raw)
In-Reply-To: <jwvr47tdkm3.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Mon, 27 Jan 2014 19:22:31 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

Hi Neil & Stefan,

>> On updating to latest Auctex from the Package Manager, there were
>> hundreds of warnings during compilation.
>
> Indeed.

Oh, yes.  Hm, compiling AUCTeX from its Git sources issues just one
warning (and a few more in preview).  With the ELPA package, there're
much more of them...

Ah, ok, AUCTeX has an lpath.el that disables byte-compile warnings.  Now
I also get pages over pages of warnings.  Most of them are references to
free variables and unknown functions from style files.  But the style
files can't be used without AUCTeX being loaded anyway, so at runtime
the vars/functions will be defined.

Any good idea to fix those?  I could add requires, but that would
possibly slow down the compilation and is not neccessary as explained
above.  I could add defvars (but no declare-functions cause that's not
available on older emacsen/xemacs) for the free variables, but again
that's not really neccessary.  I could change AUCTeX' build process so
that free-vars and unresolved warnings are ignored for the style files,
but that won't affect the ELPA builds...

>> Expected behaviour:
>> Packages in Elpa compile without warnings.
>
> ELPA packages are not magical that way, no.  It completely depends on
> the package's maintainers to try and make their code "warning-free",
> and even if they do that, it's difficult to make sure it's
> warning-free under all Emacs versions (some maintainers insist on
> warning-freeness to the point of disabling warnings or obfuscating
> code, which I find to be both very bad ideas).

AUCTeX tries to be compatible with Emacs 21.4+ and even XEmacs 21.4+, so
changing code just for eliminating some warning is hard because is
requires quite some testing effort to check all supported emacsen in all
supported versions (or at least the oldest and the newest).

> For GNU ELPA packages, I occasionally try to address some of those
> warnings.  In the case of AUCTeX, I haven't tackled that job yet.

Now that I know that there are warnings, I'll tackle those that can be
addressed in a meaningful manner myself.

Bye,
Tassilo





  parent reply	other threads:[~2014-01-28  8:14 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 18:06 bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile Neil Jackson
2014-01-27 18:23 ` Glenn Morris
2014-01-28  0:22 ` Stefan Monnier
     [not found] ` <jwvr47tdkm3.fsf-monnier+emacsbugs@gnu.org>
2014-01-28  8:14   ` Tassilo Horn [this message]
2014-01-28 17:27     ` Achim Gratz
2014-01-28 21:36       ` Stefan Monnier
2014-01-28 22:29         ` Achim Gratz
     [not found]         ` <87ppnb4u6p.fsf@Rainer.invalid>
2014-01-29  1:26           ` Stefan Monnier
2014-01-29  6:26             ` Achim Gratz
     [not found]             ` <87txcni9rj.fsf@Rainer.invalid>
2014-01-29 13:54               ` Stefan Monnier
2014-01-28  8:28   ` bug#16573: [Bug-AUCTeX] " Mosè Giordano
2014-01-29 19:30     ` Tassilo Horn
     [not found]     ` <87a9ee8u1y.fsf@thinkpad-t61.fritz.box>
2014-01-29 20:18       ` Glenn Morris
     [not found]       ` <o438k6y21d.fsf@fencepost.gnu.org>
2014-01-30  7:59         ` Tassilo Horn
     [not found]         ` <87ppn9nbn4.fsf@gnu.org>
2014-01-30  8:07           ` Glenn Morris
     [not found]           ` <yxmwidvqn4.fsf@fencepost.gnu.org>
2014-01-30 10:27             ` Tassilo Horn
     [not found]             ` <87lhxxn4rn.fsf@gnu.org>
2014-01-30 13:10               ` Mosè Giordano
2014-01-30 13:15               ` Tassilo Horn
     [not found]               ` <CAKtYQqRi74erbwpO7JWJiH0qThFxFP9nxmASzGbe+d0BXgW03g@mail.gmail.com>
2014-01-30 13:21                 ` Tassilo Horn
     [not found]                 ` <8761p1mwpm.fsf@gnu.org>
2014-01-30 15:34                   ` Stefan Monnier
     [not found]                   ` <jwveh3p4hob.fsf-monnier+emacsbugs@gnu.org>
2014-01-31  8:05                     ` Tassilo Horn
2014-01-31 14:38                       ` Stefan Monnier
     [not found]                       ` <jwvzjmcz093.fsf-monnier+emacsbugs@gnu.org>
2014-01-31 18:09                         ` Tassilo Horn
     [not found]               ` <87a9edmwzb.fsf@gnu.org>
2014-01-30 15:41                 ` Stefan Monnier
     [not found]                 ` <jwv8utx4h41.fsf-monnier+emacsbugs@gnu.org>
2014-01-31  9:50                   ` Tassilo Horn
     [not found]                   ` <87eh3obhv5.fsf@thinkpad-t61.fritz.box>
2014-01-31 10:05                     ` David Kastrup
     [not found]                     ` <877g9g4gak.fsf@fencepost.gnu.org>
2014-01-31 12:20                       ` Tassilo Horn
2014-01-31 14:49                     ` Stefan Monnier
     [not found]                     ` <jwvtxckz04b.fsf-monnier+emacsbugs@gnu.org>
2014-01-31 15:27                       ` Tassilo Horn
     [not found]   ` <87k3dkttex.fsf@gnu.org>
2014-01-28 17:07     ` Glenn Morris
2014-01-28 17:28       ` Thierry Volpiatto
2014-01-28 20:43       ` Tassilo Horn
     [not found]       ` <87eh3sm2xi.fsf__44933.1636344597$1390940459$gmane$org@gmail.com>
2014-01-29 20:00         ` Tassilo Horn
     [not found]         ` <8738k68sop.fsf@thinkpad-t61.fritz.box>
2014-01-30  5:53           ` Thierry Volpiatto
2020-08-21  1:29 ` Stefan Kangas
2021-08-27 10:35 ` Tassilo Horn

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='87k3dkttex.fsf__27231.9985939705$1390896945$gmane$org@gnu.org' \
    --to=tsdh@gnu.org \
    --cc=16573@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=neil.jackson@live.ca \
    /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).