bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Neil Jackson]

Observed behaviour:
On updating to latest Auctex from the Package Manager, there were
hundreds of warnings during compilation.

Expected behaviour:
Packages in Elpa compile without warnings.

The warnings begin thus:

Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/bib-cite.el at Mon Jan 27 13:14:02 2014

In bib-cite-minor-mode:
bib-cite.el:772:35:Warning: reference to free variable `current-menubar'

In bib-apropos:
bib-cite.el:1148:19:Warning: Use `with-current-buffer' rather than
    save-excursion+set-buffer
bib-cite.el:1164:12:Warning: `mapcar' called for effect; use `mapc' or
    `dolist' instead

In bib-cite-fontify-red:
bib-cite.el:1234:31:Warning: Use `with-current-buffer' rather than
    save-excursion+set-buffer

In bib-cite-fontify-help-xemacs:
bib-cite.el:1250:15:Warning: assignment to free variable
    `font-lock-defaults-computed'

In bib-etags:
bib-cite.el:1336:23:Warning: Use `with-current-buffer' rather than
    save-excursion+set-buffer
bib-cite.el:1357:54:Warning: Use `with-current-buffer' rather than
    save-excursion+set-buffer

In bib-guess-or-prompt-for-label:
bib-cite.el:1687:40:Warning: reference to free variable `LaTeX-label-list'

In bib-master-file:
bib-cite.el:2129:31:Warning: reference to free variable `TeX-master'

In bib-document-TeX-files:
bib-cite.el:2187:12:Warning: Use `with-current-buffer' rather than
    save-excursion+set-buffer

In bib-document-citekeys-obarray:
bib-cite.el:2241:23:Warning: Use `with-current-buffer' rather than
    save-excursion+set-buffer

In bib-get-bibliography:
bib-cite.el:2368:12:Warning: Use `with-current-buffer' rather than
    save-excursion+set-buffer
bib-cite.el:2393:43:Warning: Use `with-current-buffer' rather than
    save-excursion+set-buffer

In bib-create-auto-file:
bib-cite.el:2440:30:Warning: reference to free variable
    `BibTeX-auto-regexp-list'
bib-cite.el:2455:14:Warning: reference to free variable `TeX-header-end'
bib-cite.el:2456:30:Warning: reference to free variable `LaTeX-header-end'
bib-cite.el:2456:15:Warning: assignment to free variable `TeX-header-end'

In end of data:
bib-cite.el:2623:1:Warning: the following functions are not known to be defined:
    make-local-hook, set-buffer-menubar, delete-extent,
    delete-menu-item, set-keymap-name, reftex-view-crossref,
    font-lock-find-font-lock-defaults, extent-detached-p,
    extent-start-position, extent-end-position, make-extent,
    set-extent-property, extent-string, TeX-master-file,
    TeX-auto-write, dired-split
\f
Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/context-en.el at Mon Jan 27 13:14:02 2014
\f
Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/context-nl.el at Mon Jan 27 13:14:02 2014
\f
Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/context.el at Mon Jan 27 13:14:02 2014
context.el:71:1:Warning: global/dynamic var `reference' lacks a prefix
context.el:74:1:Warning: global/dynamic var `title' lacks a prefix

In ConTeXt-paragraph-commands-regexp:
context.el:916:25:Warning: reference to free variable
    `ConTeXt-extra-paragraph-commands'

In end of data:
context.el:1663:1:Warning: the function `make-local-hook' is not known to be
    defined.
\f
Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/font-latex.el at Mon Jan 27 13:14:03 2014

In font-latex-update-sectioning-faces:
font-latex.el:184:37:Warning: reference to free variable
    `font-latex-fontify-sectioning'

In font-latex-set-syntactic-keywords:
font-latex.el:934:9:Warning: assignment to free variable
    `font-latex-doctex-syntactic-keywords'

In font-latex-syntactic-face-function:
font-latex.el:949:7:Warning: `char-valid-p' is an obsolete function (as of
    23.1); use `characterp' instead.

In end of data:
font-latex.el:1994:1:Warning: the following functions are not known to be defined:
    face-property-instance, set-face-property
\f
Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/latex.el at Mon Jan 27 13:14:03 2014

In LaTeX-section-heading:
latex.el:427:11:Warning: assignment to free variable `level'

In LaTeX-section-toc:
latex.el:443:22:Warning: assignment to free variable `toc'
latex.el:444:13:Warning: reference to free variable `toc'

In LaTeX-section-section:
latex.el:462:16:Warning: reference to free variable `toc'

In LaTeX-close-environment:
latex.el:599:14:Warning: `next-line' used from Lisp code
That command is designed for interactive use only

In LaTeX-auto-prepare:
latex.el:1244:9:Warning: assignment to free variable `LaTeX-auto-arguments'
latex.el:1245:9:Warning: assignment to free variable `LaTeX-auto-optional'
latex.el:1246:9:Warning: assignment to free variable `LaTeX-auto-env-args'
latex.el:1247:9:Warning: assignment to free variable `LaTeX-auto-style'

In LaTeX-listify-package-options:
latex.el:1288:45:Warning: `delete-backward-char' used from Lisp code
That command is designed for interactive use only

In LaTeX-auto-cleanup:
latex.el:1299:32:Warning: reference to free variable `LaTeX-auto-bibliography'
latex.el:1299:32:Warning: assignment to free variable
    `LaTeX-auto-bibliography'
latex.el:1302:17:Warning: reference to free variable `LaTeX-auto-style'
latex.el:1310:37:Warning: assignment to free variable `LaTeX-auto-style'
latex.el:1324:29:Warning: assignment to free variable `TeX-auto-file'
latex.el:1370:25:Warning: assignment to free variable `TeX-auto-symbol'
latex.el:1366:9:Warning: reference to free variable `LaTeX-auto-arguments'
latex.el:1374:9:Warning: reference to free variable `LaTeX-auto-optional'
latex.el:1403:27:Warning: assignment to free variable `LaTeX-auto-environment'
latex.el:1381:9:Warning: reference to free variable `LaTeX-auto-env-args'
latex.el:1391:46:Warning: assignment to free variable `TeX-auto-symbol'

...




In GNU Emacs 24.3.1 (x86_64-redhat-linux-gnu, GTK+ Version 3.8.2)
 of 2013-08-14 on buildvm-15.phx2.fedoraproject.org
Windowing system distributor `Fedora Project', version 11.0.11404000
System Description:	Fedora release 19 (Schrödinger’s Cat)

Configured using:
 `configure '--build=x86_64-redhat-linux-gnu'
 '--host=x86_64-redhat-linux-gnu' '--program-prefix='
 '--disable-dependency-tracking' '--prefix=/usr' '--exec-prefix=/usr'
 '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc'
 '--datadir=/usr/share' '--includedir=/usr/include'
 '--libdir=/usr/lib64' '--libexecdir=/usr/libexec'
 '--localstatedir=/var' '--sharedstatedir=/var/lib'
 '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-dbus'
 '--with-gif' '--with-jpeg' '--with-png' '--with-rsvg' '--with-tiff'
 '--with-xft' '--with-xpm' '--with-x-toolkit=gtk3' '--with-gpm=no'
 'build_alias=x86_64-redhat-linux-gnu'
 'host_alias=x86_64-redhat-linux-gnu' 'CFLAGS=-DMAIL_USE_LOCKF -O2 -g
 -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
 --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic'
 'LDFLAGS=-Wl,-z,relro ''

Important settings:
  value of $LC_MONETARY: en_DK.utf8
  value of $LC_NUMERIC: en_DK.utf8
  value of $LC_TIME: en_DK.utf8
  value of $LANG: en_CA.utf8
  value of $XMODIFIERS: @im=ibus
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t

Major mode: Summary

Minor modes in effect:
  recentf-mode: t
  show-paren-mode: t
  display-time-mode: t
  display-battery-mode: t
  cua-mode: t
  shell-dirtrack-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  buffer-read-only: t
  size-indication-mode: t
  column-number-mode: t
  line-number-mode: t
  global-visual-line-mode: t
  visual-line-mode: t
  transient-mark-mode: t

Recent input:
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> <S-down> <S-down> 
<S-up> <S-up> <S-up> <S-up> <S-up> <S-up> <S-up> <S-up> 
<S-up> <S-up> <S-up> <S-up> <S-up> <delete> <up> <down> 
<down> <delete> <return> <delete> <return> <up> <up> 
<up> <up> <up> <up> <up> <up> <up> <up> <up> <up> <up> 
<up> <up> <up> <up> <up> <up> <up> <up> <up> <up> <up> 
<up> <up> <up> <up> <up> <up> <up> <up> <up> <up> <up> 
<up> <up> <up> <up> <up> <up> <up> <up> <up> <up> <up> 
<up> <up> <up> <up> <up> <up> <up> <up> <up> <up> <up> 
<up> <up> <up> <up> <up> <up> <up> <up> <up> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <C-home> <down> 
<switch-frame> <switch-frame> <down> <down> <down> 
<down> <down> <up> <S-down> <S-down> <S-down> <S-down> 
<S-down> <S-down> <S-down> <S-down> C-c <timeout> C-c 
C-c M-x r e p o r t - e <tab> <return>

Recent messages:
Sending...
Mark set [2 times]
Sending via mail...
Sending email 
Sending email done
gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated.
Mark set
Saving file /home/nlj/Mail/archive/sent/2014-01...
Wrote /home/nlj/Mail/archive/sent/2014-01
Sending...done

Load-path shadows:
/home/nlj/.emacs.d/elpa/auctex-11.87/plain-tex hides /usr/share/emacs/site-lisp/auctex/plain-tex
/home/nlj/.emacs.d/elpa/auctex-11.87/tex hides /usr/share/emacs/site-lisp/auctex/tex
/home/nlj/.emacs.d/elpa/auctex-11.87/tex-buf hides /usr/share/emacs/site-lisp/auctex/tex-buf
/home/nlj/.emacs.d/elpa/auctex-11.87/preview hides /usr/share/emacs/site-lisp/auctex/preview
/home/nlj/.emacs.d/elpa/auctex-11.87/font-latex hides /usr/share/emacs/site-lisp/auctex/font-latex
/home/nlj/.emacs.d/elpa/auctex-11.87/context-en hides /usr/share/emacs/site-lisp/auctex/context-en
/home/nlj/.emacs.d/elpa/auctex-11.87/toolbar-x hides /usr/share/emacs/site-lisp/auctex/toolbar-x
/home/nlj/.emacs.d/elpa/auctex-11.87/texmathp hides /usr/share/emacs/site-lisp/auctex/texmathp
/home/nlj/.emacs.d/elpa/auctex-11.87/tex-bar hides /usr/share/emacs/site-lisp/auctex/tex-bar
/home/nlj/.emacs.d/elpa/auctex-11.87/context hides /usr/share/emacs/site-lisp/auctex/context
/home/nlj/.emacs.d/elpa/auctex-11.87/tex-info hides /usr/share/emacs/site-lisp/auctex/tex-info
/home/nlj/.emacs.d/elpa/auctex-11.87/latex hides /usr/share/emacs/site-lisp/auctex/latex
/home/nlj/.emacs.d/elpa/auctex-11.87/tex-style hides /usr/share/emacs/site-lisp/auctex/tex-style
/home/nlj/.emacs.d/elpa/auctex-11.87/tex-jp hides /usr/share/emacs/site-lisp/auctex/tex-jp
/home/nlj/.emacs.d/elpa/auctex-11.87/multi-prompt hides /usr/share/emacs/site-lisp/auctex/multi-prompt
/home/nlj/.emacs.d/elpa/auctex-11.87/tex-fold hides /usr/share/emacs/site-lisp/auctex/tex-fold
/home/nlj/.emacs.d/elpa/auctex-11.87/bib-cite hides /usr/share/emacs/site-lisp/auctex/bib-cite
/home/nlj/.emacs.d/elpa/auctex-11.87/context-nl hides /usr/share/emacs/site-lisp/auctex/context-nl
/home/nlj/.emacs.d/elpa/auctex-11.87/tex-mik hides /usr/share/emacs/site-lisp/auctex/tex-mik
/home/nlj/.emacs.d/elpa/auctex-11.87/tex-font hides /usr/share/emacs/site-lisp/auctex/tex-font
/home/nlj/.emacs.d/elpa/auctex-11.87/prv-emacs hides /usr/share/emacs/site-lisp/auctex/prv-emacs
/home/nlj/.emacs.d/elpa/auctex-11.87/tex-site hides /usr/share/emacs/site-lisp/tex-site
/usr/share/emacs/site-lisp/site-start.d/maxima-modes hides /usr/share/emacs/site-lisp/maxima/site_start.d/maxima-modes
/home/nlj/.emacs.d/elpa/org-20130930/ob-maxima hides /usr/share/emacs/24.3/lisp/org/ob-maxima
/home/nlj/.emacs.d/elpa/org-20130930/ob-haskell hides /usr/share/emacs/24.3/lisp/org/ob-haskell
/home/nlj/.emacs.d/elpa/org-20130930/org-indent hides /usr/share/emacs/24.3/lisp/org/org-indent
/home/nlj/.emacs.d/elpa/org-20130930/org-habit hides /usr/share/emacs/24.3/lisp/org/org-habit
/home/nlj/.emacs.d/elpa/org-20130930/org-datetree hides /usr/share/emacs/24.3/lisp/org/org-datetree
/home/nlj/.emacs.d/elpa/org-20130930/ob-lob hides /usr/share/emacs/24.3/lisp/org/ob-lob
/home/nlj/.emacs.d/elpa/org-20130930/ob-ruby hides /usr/share/emacs/24.3/lisp/org/ob-ruby
/home/nlj/.emacs.d/elpa/org-20130930/org-table hides /usr/share/emacs/24.3/lisp/org/org-table
/home/nlj/.emacs.d/elpa/org-20130930/org-install hides /usr/share/emacs/24.3/lisp/org/org-install
/home/nlj/.emacs.d/elpa/org-20130930/org-mhe hides /usr/share/emacs/24.3/lisp/org/org-mhe
/home/nlj/.emacs.d/elpa/org-20130930/org-crypt hides /usr/share/emacs/24.3/lisp/org/org-crypt
/home/nlj/.emacs.d/elpa/org-20130930/org-eshell hides /usr/share/emacs/24.3/lisp/org/org-eshell
/home/nlj/.emacs.d/elpa/org-20130930/ob-picolisp hides /usr/share/emacs/24.3/lisp/org/ob-picolisp
/home/nlj/.emacs.d/elpa/org-20130930/org-id hides /usr/share/emacs/24.3/lisp/org/org-id
/home/nlj/.emacs.d/elpa/org-20130930/ob-clojure hides /usr/share/emacs/24.3/lisp/org/ob-clojure
/home/nlj/.emacs.d/elpa/org-20130930/org-pcomplete hides /usr/share/emacs/24.3/lisp/org/org-pcomplete
/home/nlj/.emacs.d/elpa/org-20130930/ob-scheme hides /usr/share/emacs/24.3/lisp/org/ob-scheme
/home/nlj/.emacs.d/elpa/org-20130930/org-bibtex hides /usr/share/emacs/24.3/lisp/org/org-bibtex
/home/nlj/.emacs.d/elpa/org-20130930/org-docview hides /usr/share/emacs/24.3/lisp/org/org-docview
/home/nlj/.emacs.d/elpa/org-20130930/ob-mscgen hides /usr/share/emacs/24.3/lisp/org/ob-mscgen
/home/nlj/.emacs.d/elpa/org-20130930/org-irc hides /usr/share/emacs/24.3/lisp/org/org-irc
/home/nlj/.emacs.d/elpa/org-20130930/org-faces hides /usr/share/emacs/24.3/lisp/org/org-faces
/home/nlj/.emacs.d/elpa/org-20130930/ob-lilypond hides /usr/share/emacs/24.3/lisp/org/ob-lilypond
/home/nlj/.emacs.d/elpa/org-20130930/ob-ditaa hides /usr/share/emacs/24.3/lisp/org/ob-ditaa
/home/nlj/.emacs.d/elpa/org-20130930/ob-python hides /usr/share/emacs/24.3/lisp/org/ob-python
/home/nlj/.emacs.d/elpa/org-20130930/ob-css hides /usr/share/emacs/24.3/lisp/org/ob-css
/home/nlj/.emacs.d/elpa/org-20130930/org-capture hides /usr/share/emacs/24.3/lisp/org/org-capture
/home/nlj/.emacs.d/elpa/org-20130930/org-protocol hides /usr/share/emacs/24.3/lisp/org/org-protocol
/home/nlj/.emacs.d/elpa/org-20130930/org hides /usr/share/emacs/24.3/lisp/org/org
/home/nlj/.emacs.d/elpa/org-20130930/org-src hides /usr/share/emacs/24.3/lisp/org/org-src
/home/nlj/.emacs.d/elpa/org-20130930/ob-eval hides /usr/share/emacs/24.3/lisp/org/ob-eval
/home/nlj/.emacs.d/elpa/org-20130930/ob-gnuplot hides /usr/share/emacs/24.3/lisp/org/ob-gnuplot
/home/nlj/.emacs.d/elpa/org-20130930/org-version hides /usr/share/emacs/24.3/lisp/org/org-version
/home/nlj/.emacs.d/elpa/org-20130930/org-mobile hides /usr/share/emacs/24.3/lisp/org/org-mobile
/home/nlj/.emacs.d/elpa/org-20130930/org-plot hides /usr/share/emacs/24.3/lisp/org/org-plot
/home/nlj/.emacs.d/elpa/org-20130930/ob-emacs-lisp hides /usr/share/emacs/24.3/lisp/org/ob-emacs-lisp
/home/nlj/.emacs.d/elpa/org-20130930/ob-exp hides /usr/share/emacs/24.3/lisp/org/ob-exp
/home/nlj/.emacs.d/elpa/org-20130930/org-footnote hides /usr/share/emacs/24.3/lisp/org/org-footnote
/home/nlj/.emacs.d/elpa/org-20130930/ob-sh hides /usr/share/emacs/24.3/lisp/org/ob-sh
/home/nlj/.emacs.d/elpa/org-20130930/ob-perl hides /usr/share/emacs/24.3/lisp/org/ob-perl
/home/nlj/.emacs.d/elpa/org-20130930/org-compat hides /usr/share/emacs/24.3/lisp/org/org-compat
/home/nlj/.emacs.d/elpa/org-20130930/org-inlinetask hides /usr/share/emacs/24.3/lisp/org/org-inlinetask
/home/nlj/.emacs.d/elpa/org-20130930/org-gnus hides /usr/share/emacs/24.3/lisp/org/org-gnus
/home/nlj/.emacs.d/elpa/org-20130930/ob-screen hides /usr/share/emacs/24.3/lisp/org/ob-screen
/home/nlj/.emacs.d/elpa/org-20130930/org-colview hides /usr/share/emacs/24.3/lisp/org/org-colview
/home/nlj/.emacs.d/elpa/org-20130930/ob-shen hides /usr/share/emacs/24.3/lisp/org/ob-shen
/home/nlj/.emacs.d/elpa/org-20130930/ob-sass hides /usr/share/emacs/24.3/lisp/org/ob-sass
/home/nlj/.emacs.d/elpa/org-20130930/org-list hides /usr/share/emacs/24.3/lisp/org/org-list
/home/nlj/.emacs.d/elpa/org-20130930/org-bbdb hides /usr/share/emacs/24.3/lisp/org/org-bbdb
/home/nlj/.emacs.d/elpa/org-20130930/ob-lisp hides /usr/share/emacs/24.3/lisp/org/ob-lisp
/home/nlj/.emacs.d/elpa/org-20130930/org-info hides /usr/share/emacs/24.3/lisp/org/org-info
/home/nlj/.emacs.d/elpa/org-20130930/ob-keys hides /usr/share/emacs/24.3/lisp/org/ob-keys
/home/nlj/.emacs.d/elpa/org-20130930/ob-io hides /usr/share/emacs/24.3/lisp/org/ob-io
/home/nlj/.emacs.d/elpa/org-20130930/ob-comint hides /usr/share/emacs/24.3/lisp/org/ob-comint
/home/nlj/.emacs.d/elpa/org-20130930/ob-sqlite hides /usr/share/emacs/24.3/lisp/org/ob-sqlite
/home/nlj/.emacs.d/elpa/org-20130930/org-rmail hides /usr/share/emacs/24.3/lisp/org/org-rmail
/home/nlj/.emacs.d/elpa/org-20130930/org-entities hides /usr/share/emacs/24.3/lisp/org/org-entities
/home/nlj/.emacs.d/elpa/org-20130930/org-clock hides /usr/share/emacs/24.3/lisp/org/org-clock
/home/nlj/.emacs.d/elpa/org-20130930/org-agenda hides /usr/share/emacs/24.3/lisp/org/org-agenda
/home/nlj/.emacs.d/elpa/org-20130930/ob-tangle hides /usr/share/emacs/24.3/lisp/org/ob-tangle
/home/nlj/.emacs.d/elpa/org-20130930/org-timer hides /usr/share/emacs/24.3/lisp/org/org-timer
/home/nlj/.emacs.d/elpa/org-20130930/ob-org hides /usr/share/emacs/24.3/lisp/org/ob-org
/home/nlj/.emacs.d/elpa/org-20130930/ob-matlab hides /usr/share/emacs/24.3/lisp/org/ob-matlab
/home/nlj/.emacs.d/elpa/org-20130930/ob-ref hides /usr/share/emacs/24.3/lisp/org/ob-ref
/home/nlj/.emacs.d/elpa/org-20130930/ob-java hides /usr/share/emacs/24.3/lisp/org/ob-java
/home/nlj/.emacs.d/elpa/org-20130930/org-attach hides /usr/share/emacs/24.3/lisp/org/org-attach
/home/nlj/.emacs.d/elpa/org-20130930/ob-octave hides /usr/share/emacs/24.3/lisp/org/ob-octave
/home/nlj/.emacs.d/elpa/org-20130930/ob-fortran hides /usr/share/emacs/24.3/lisp/org/ob-fortran
/home/nlj/.emacs.d/elpa/org-20130930/ob-js hides /usr/share/emacs/24.3/lisp/org/ob-js
/home/nlj/.emacs.d/elpa/org-20130930/ob-sql hides /usr/share/emacs/24.3/lisp/org/ob-sql
/home/nlj/.emacs.d/elpa/org-20130930/org-feed hides /usr/share/emacs/24.3/lisp/org/org-feed
/home/nlj/.emacs.d/elpa/org-20130930/ob-C hides /usr/share/emacs/24.3/lisp/org/ob-C
/home/nlj/.emacs.d/elpa/org-20130930/ob-ledger hides /usr/share/emacs/24.3/lisp/org/ob-ledger
/home/nlj/.emacs.d/elpa/org-20130930/ob-plantuml hides /usr/share/emacs/24.3/lisp/org/ob-plantuml
/home/nlj/.emacs.d/elpa/org-20130930/org-mouse hides /usr/share/emacs/24.3/lisp/org/org-mouse
/home/nlj/.emacs.d/elpa/org-20130930/org-element hides /usr/share/emacs/24.3/lisp/org/org-element
/home/nlj/.emacs.d/elpa/org-20130930/org-loaddefs hides /usr/share/emacs/24.3/lisp/org/org-loaddefs
/home/nlj/.emacs.d/elpa/org-20130930/ob-scala hides /usr/share/emacs/24.3/lisp/org/ob-scala
/home/nlj/.emacs.d/elpa/org-20130930/ob-awk hides /usr/share/emacs/24.3/lisp/org/ob-awk
/home/nlj/.emacs.d/elpa/org-20130930/org-macs hides /usr/share/emacs/24.3/lisp/org/org-macs
/home/nlj/.emacs.d/elpa/org-20130930/ob-calc hides /usr/share/emacs/24.3/lisp/org/ob-calc
/home/nlj/.emacs.d/elpa/org-20130930/org-w3m hides /usr/share/emacs/24.3/lisp/org/org-w3m
/home/nlj/.emacs.d/elpa/org-20130930/ob-dot hides /usr/share/emacs/24.3/lisp/org/ob-dot
/home/nlj/.emacs.d/elpa/org-20130930/org-ctags hides /usr/share/emacs/24.3/lisp/org/org-ctags
/home/nlj/.emacs.d/elpa/org-20130930/org-archive hides /usr/share/emacs/24.3/lisp/org/org-archive
/home/nlj/.emacs.d/elpa/org-20130930/ob-R hides /usr/share/emacs/24.3/lisp/org/ob-R
/home/nlj/.emacs.d/elpa/org-20130930/ob-asymptote hides /usr/share/emacs/24.3/lisp/org/ob-asymptote
/home/nlj/.emacs.d/elpa/org-20130930/ob-latex hides /usr/share/emacs/24.3/lisp/org/ob-latex
/home/nlj/.emacs.d/elpa/org-20130930/ob-ocaml hides /usr/share/emacs/24.3/lisp/org/ob-ocaml
/home/nlj/.emacs.d/elpa/org-20130930/ob-table hides /usr/share/emacs/24.3/lisp/org/ob-table
/home/nlj/.emacs.d/elpa/org-20130930/ob hides /usr/share/emacs/24.3/lisp/org/ob

Features:
(smtpmail gnus-cite gnus-kill gnus-ml disp-table nndraft nnmh
url-handlers nnrss mm-url utf-7 nnimap utf7 gnutls nnfolder parse-time
netrc gnus-agent gnus-srvr gnus-score score-mode nnvirtual gnus-msg
gnus-art mm-uu mml2015 epg-config mm-view mml-smime smime dig nntp
gnus-cache mailalias mailclient qp cus-edit help-mode shadow sort
mail-extr emacsbug sendmail misearch multi-isearch sgml-mode ibuf-ext
ibuffer timezone texinfo toolbar-x prv-emacs reporter desktop context
plain-tex latex tex-style tex-buf tex dbus xml rng-loc rng-uri rng-parse
rng-match rng-dt rng-util rng-pttrn nxml-parse nxml-ns nxml-enc xmltok
nxml-util ox-latex ox-icalendar ox-html table ox-ascii ox-publish ox
derived org-table gnus-sum nnoo gnus-group gnus-undo nnmail mail-source
gnus-start gnus-spec gnus-int gnus-range message rfc822 mml mml-sec
mm-decode mm-bodies mm-encode mailabbrev gmm-utils mailheader gnus-win
gnus gnus-ems nnheader esh-var esh-io esh-cmd esh-opt esh-ext esh-proc
esh-arg esh-groups eshell esh-module esh-mode esh-util doc-view
jka-compr image-mode dired vc-git org-id rx ob-octave calc calc-loaddefs
calc-macs cc-mode cc-fonts cc-guess cc-menus cc-cmds cc-styles cc-align
cc-engine autoload tar-mode mule-util mail-utils network-stream starttls
url-http tls mail-parse rfc2231 rfc2047 rfc2045 ietf-drums url-gw
url-cache url-auth url url-proxy url-privacy url-expand url-methods
url-history url-cookie url-domsuf url-util url-parse auth-source eieio
mm-util mail-prsvr password-cache url-vars mailcap finder-inf
org-element org-rmail org-mhe org-irc org-info org-gnus gnus-util
org-docview org-bibtex bibtex org-bbdb org-w3m org-latex
org-export-latex org-beamer org-exp org-exp-blocks org-agenda footnote
org byte-opt warnings bytecomp byte-compile cconv org-macro org-footnote
org-pcomplete org-list org-faces org-entities noutline outline
easy-mmode org-version ob-emacs-lisp ob ob-tangle org-src ob-ref ob-lob
ob-table ob-keys ob-exp ob-comint ob-core ob-eval org-compat org-macs
org-loaddefs format-spec find-func cal-menu calendar cal-loaddefs
auctex-autoloads csv-mode-autoloads org-autoloads info package cl-macs
gv edmacro kmacro recentf tree-widget saveplace wheatgrass-theme paren
time battery cua-base cus-start cus-load preview-latex ido ess-toolbar
ess-mouse mouseme thingatpt browse-url ess-menu ess-swv ess-noweb
ess-noweb-font-lock-mode ess-bugs-l essd-els ess-sas-d ess-sas-l
ess-sas-a shell pcomplete ess-arc-d ess-vst-d ess-xls-d ess-lsp-l
ess-sta-d ess-sta-l cc-vars cc-defs make-regexp ess-sp6-d ess-sp5-d
ess-sp3-d ess-julia ess-r-d compile ess-tracebug ess-roxy advice
advice-preload hideshow ess-help ess-developer ess-r-args eldoc help-fns
ess-s-l ess ess-inf comint ansi-color ring ess-mode ess-noweb-mode
ess-utils ess-custom executable ess-compat ess-site color-theme easymenu
wid-edit cl cl-lib bbdb-autoloads tex-site auto-loads time-date tooltip
ediff-hook vc-hooks lisp-float-type mwheel x-win x-dnd tool-bar dnd
fontset image regexp-opt fringe tabulated-list newcomment lisp-mode
register page menu-bar rfn-eshadow timer select scroll-bar mouse
jit-lock font-lock syntax facemenu font-core frame cham georgian
utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean
japanese hebrew greek romanian slovak czech european ethiopic indian
cyrillic chinese case-table epa-hook jka-cmpr-hook help simple abbrev
minibuffer loaddefs button faces cus-face macroexp files text-properties
overlay sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote make-network-process dbusbind
dynamic-setting system-font-setting font-render-setting move-toolbar gtk
x-toolkit x multi-tty emacs)

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Glenn Morris]

None of the following are (clear evidence of) bugs.
See my comments in http://debbugs.gnu.org/16572#8

Neil Jackson wrote:

> bib-cite.el:772:35:Warning: reference to free variable `current-menubar'
>
> In bib-apropos:
> bib-cite.el:1148:19:Warning: Use `with-current-buffer' rather than
>     save-excursion+set-buffer
> bib-cite.el:1164:12:Warning: `mapcar' called for effect; use `mapc' or
>     `dolist' instead
>
> In bib-cite-fontify-red:
> bib-cite.el:1234:31:Warning: Use `with-current-buffer' rather than
>     save-excursion+set-buffer
>
> In bib-cite-fontify-help-xemacs:
> bib-cite.el:1250:15:Warning: assignment to free variable
>     `font-lock-defaults-computed'
>
> In bib-etags:
> bib-cite.el:1336:23:Warning: Use `with-current-buffer' rather than
>     save-excursion+set-buffer
> bib-cite.el:1357:54:Warning: Use `with-current-buffer' rather than
>     save-excursion+set-buffer
>
> In bib-guess-or-prompt-for-label:
> bib-cite.el:1687:40:Warning: reference to free variable `LaTeX-label-list'
>
> In bib-master-file:
> bib-cite.el:2129:31:Warning: reference to free variable `TeX-master'
>
> In bib-document-TeX-files:
> bib-cite.el:2187:12:Warning: Use `with-current-buffer' rather than
>     save-excursion+set-buffer
>
> In bib-document-citekeys-obarray:
> bib-cite.el:2241:23:Warning: Use `with-current-buffer' rather than
>     save-excursion+set-buffer
>
> In bib-get-bibliography:
> bib-cite.el:2368:12:Warning: Use `with-current-buffer' rather than
>     save-excursion+set-buffer
> bib-cite.el:2393:43:Warning: Use `with-current-buffer' rather than
>     save-excursion+set-buffer
>
> In bib-create-auto-file:
> bib-cite.el:2440:30:Warning: reference to free variable
>     `BibTeX-auto-regexp-list'
> bib-cite.el:2455:14:Warning: reference to free variable `TeX-header-end'
> bib-cite.el:2456:30:Warning: reference to free variable `LaTeX-header-end'
> bib-cite.el:2456:15:Warning: assignment to free variable `TeX-header-end'
>
> In end of data:
> bib-cite.el:2623:1:Warning: the following functions are not known to be defined:
>     make-local-hook, set-buffer-menubar, delete-extent,
>     delete-menu-item, set-keymap-name, reftex-view-crossref,
>     font-lock-find-font-lock-defaults, extent-detached-p,
>     extent-start-position, extent-end-position, make-extent,
>     set-extent-property, extent-string, TeX-master-file,
>     TeX-auto-write, dired-split
> \f
> Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/context-en.el at Mon Jan 27 13:14:02 2014
> \f
> Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/context-nl.el at Mon Jan 27 13:14:02 2014
> \f
> Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/context.el at Mon Jan 27 13:14:02 2014
> context.el:71:1:Warning: global/dynamic var `reference' lacks a prefix
> context.el:74:1:Warning: global/dynamic var `title' lacks a prefix
>
> In ConTeXt-paragraph-commands-regexp:
> context.el:916:25:Warning: reference to free variable
>     `ConTeXt-extra-paragraph-commands'
>
> In end of data:
> context.el:1663:1:Warning: the function `make-local-hook' is not known to be
>     defined.
> \f
> Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/font-latex.el at Mon Jan 27 13:14:03 2014
>
> In font-latex-update-sectioning-faces:
> font-latex.el:184:37:Warning: reference to free variable
>     `font-latex-fontify-sectioning'
>
> In font-latex-set-syntactic-keywords:
> font-latex.el:934:9:Warning: assignment to free variable
>     `font-latex-doctex-syntactic-keywords'
>
> In font-latex-syntactic-face-function:
> font-latex.el:949:7:Warning: `char-valid-p' is an obsolete function (as of
>     23.1); use `characterp' instead.
>
> In end of data:
> font-latex.el:1994:1:Warning: the following functions are not known to be defined:
>     face-property-instance, set-face-property
> \f
> Compiling file /home/nlj/.emacs.d/elpa/auctex-11.87.2/latex.el at Mon Jan 27 13:14:03 2014
>
> In LaTeX-section-heading:
> latex.el:427:11:Warning: assignment to free variable `level'
>
> In LaTeX-section-toc:
> latex.el:443:22:Warning: assignment to free variable `toc'
> latex.el:444:13:Warning: reference to free variable `toc'
>
> In LaTeX-section-section:
> latex.el:462:16:Warning: reference to free variable `toc'
>
> In LaTeX-close-environment:
> latex.el:599:14:Warning: `next-line' used from Lisp code
> That command is designed for interactive use only
>
> In LaTeX-auto-prepare:
> latex.el:1244:9:Warning: assignment to free variable `LaTeX-auto-arguments'
> latex.el:1245:9:Warning: assignment to free variable `LaTeX-auto-optional'
> latex.el:1246:9:Warning: assignment to free variable `LaTeX-auto-env-args'
> latex.el:1247:9:Warning: assignment to free variable `LaTeX-auto-style'
>
> In LaTeX-listify-package-options:
> latex.el:1288:45:Warning: `delete-backward-char' used from Lisp code
> That command is designed for interactive use only
>
> In LaTeX-auto-cleanup:
> latex.el:1299:32:Warning: reference to free variable `LaTeX-auto-bibliography'
> latex.el:1299:32:Warning: assignment to free variable
>     `LaTeX-auto-bibliography'
> latex.el:1302:17:Warning: reference to free variable `LaTeX-auto-style'
> latex.el:1310:37:Warning: assignment to free variable `LaTeX-auto-style'
> latex.el:1324:29:Warning: assignment to free variable `TeX-auto-file'
> latex.el:1370:25:Warning: assignment to free variable `TeX-auto-symbol'
> latex.el:1366:9:Warning: reference to free variable `LaTeX-auto-arguments'
> latex.el:1374:9:Warning: reference to free variable `LaTeX-auto-optional'
> latex.el:1403:27:Warning: assignment to free variable `LaTeX-auto-environment'
> latex.el:1381:9:Warning: reference to free variable `LaTeX-auto-env-args'
> latex.el:1391:46:Warning: assignment to free variable `TeX-auto-symbol'

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Stefan Monnier]

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

Indeed.

> 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).

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.


        Stefan

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

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

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Achim Gratz]

Tassilo Horn writes:
> 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...

In Org we use compatibility macros, mostly using the org namespace, but
in a few cases simply addign a missing definition.  More specifically
for declare-function:

(eval-and-compile
  (unless (fboundp 'declare-function)
    (defmacro declare-function (fn file &optional arglist fileonly)
      `(autoload ',fn ,file))))


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Stefan Monnier]

> (eval-and-compile
>   (unless (fboundp 'declare-function)
>     (defmacro declare-function (fn file &optional arglist fileonly)
>       `(autoload ',fn ,file))))

Yuck!  This is an ugly trick trying to silence warnings.
Better macroexpand it to nil: you'll get warnings in older Emacsen, but
at least you won't end up changing the code's behavior.


        Stefan

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Achim Gratz]

Stefan Monnier writes:
>> (eval-and-compile
>>   (unless (fboundp 'declare-function)
>>     (defmacro declare-function (fn file &optional arglist fileonly)
>>       `(autoload ',fn ,file))))
>
> Yuck!  This is an ugly trick trying to silence warnings.

Not much uglier than declare-function itself.  These things would
perhaps benefit if one could declare-require the source file in question
(it's almost invariably callbacks and guarded calls into external
packages that end up needing this treatment), but that still doesn't
address how to make it backward compatible.

> Better macroexpand it to nil: you'll get warnings in older Emacsen, but
> at least you won't end up changing the code's behavior.

That's certainly not recommended for everyone and everything, but since
declare-function must used in situations were the function to be
declared is known to be already defined at runtime, the autoload will
never do anything anyway; if it does it was a bug to begin with.
Defining this nil and then not finding the one warning that must be
dealt with in the hundreds of spurious warnings is decidedly worse.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Stefan Monnier]

> That's certainly not recommended for everyone and everything, but since
> declare-function must used in situations were the function to be
> declared is known to be already defined at runtime, the autoload will
> never do anything anyway;

It does do something:
- it does something during byte-compilation.
- it does something during run-time if the function is "already loaded
  when you call it" but not "already loaded when you load the file".
Both of those situations are quite common.  The reason why you don't
suffer from it is not that the autoload doesn't do anything, but because
the autoload is usually harmless.

> Defining this nil and then not finding the one warning that must be
> dealt with in the hundreds of spurious warnings is decidedly worse.

Admittedly I haven't spent much time dealing with compatibility with
older Emacsen lately, but in the past I've never found warnings useful
for that work.  So I only ever used warnings to help debug & improve my
code on my "main" Emacs version, and completely ignored warnings when
porting to older Emacsen (relying on testing and bug-reports instead).

Of course, it's probably got to do with taste, but if you're going to
use `autoload', then I strongly suggest you name it
`<foo>-declare-function', since when "adding a missing definition" you're
better off defining it *exactly* like a recentish Emacs.


        Stefan

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Achim Gratz]

Stefan Monnier writes:
>> That's certainly not recommended for everyone and everything, but since
>> declare-function must used in situations were the function to be
>> declared is known to be already defined at runtime, the autoload will
>> never do anything anyway;
>
> It does do something:
> - it does something during byte-compilation.

That's the intended effect.  I haven't checked if it could in fact skip
the compile part of eval-and-compile; if so, that would be an obvious
improvement.

> - it does something during run-time if the function is "already loaded
>   when you call it" but not "already loaded when you load the file".

Which is not supposed to happen in these cases, otherwise you'd be able
to use a plain require.

> Both of those situations are quite common.  The reason why you don't
> suffer from it is not that the autoload doesn't do anything, but because
> the autoload is usually harmless.

That too.

>> Defining this nil and then not finding the one warning that must be
>> dealt with in the hundreds of spurious warnings is decidedly worse.
>
> Admittedly I haven't spent much time dealing with compatibility with
> older Emacsen lately, but in the past I've never found warnings useful
> for that work.  So I only ever used warnings to help debug & improve my
> code on my "main" Emacs version, and completely ignored warnings when
> porting to older Emacsen (relying on testing and bug-reports instead).

I can't speak for other eLisp libraries, but testing came late for Org
and test coverage isn't quite up where it would need to be for this to
work.  Besides, testing on older Emacsen gets rather difficult since
they don't compile on my system any more and I'd need to set up a
container or VM.

> Of course, it's probably got to do with taste, but if you're going to
> use `autoload', then I strongly suggest you name it
> `<foo>-declare-function', since when "adding a missing definition" you're
> better off defining it *exactly* like a recentish Emacs.

Moving it to Org namespace may be in the cards given that Org already
does that for most other compatibility macros.  If you know a way to
have it really just declare the function without byte-compiler magic let
me know.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Stefan Monnier]

>> Admittedly I haven't spent much time dealing with compatibility with
>> older Emacsen lately, but in the past I've never found warnings useful
>> for that work.  So I only ever used warnings to help debug & improve my
>> code on my "main" Emacs version, and completely ignored warnings when
>> porting to older Emacsen (relying on testing and bug-reports instead).
> I can't speak for other eLisp libraries, but testing came late for Org
> and test coverage isn't quite up where it would need to be for this to
> work.

By testing I meant "start up an old Emacs and try to play a bit with the
feature see if it seems to work".  Of course, if you have a test suite
scripted up and all, that's even better.

> Besides, testing on older Emacsen gets rather difficult since they
> don't compile on my system any more and I'd need to set up a container
> or VM.

"dpkg" was able to install emacs19, emacs20, emacs21, emacs22, emacs23,
emacs24 on my machines, so I haven't had to build them by hand.


        Stefan

bug#16573: [Bug-AUCTeX] bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Mosè Giordano]

2014-01-28 Stefan Monnier <monnier@iro.umontreal.ca>:
> In the case of AUCTeX, I haven't tackled that job yet.

Since the release of AUCTeX 11.87, some compilation warnings have been
addressed, e.g. see these commits:
http://git.savannah.gnu.org/cgit/auctex.git/commit/?id=6178c5110a24175d0d5df1410e66039ad383daba
http://git.savannah.gnu.org/cgit/auctex.git/commit/?id=04927d01a3dfd8b0886d1070abe8e11e925f0e4e

Bye,
Mosè

bug#16573: [Bug-AUCTeX] bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

>> In the case of AUCTeX, I haven't tackled that job yet.
>
> Since the release of AUCTeX 11.87, some compilation warnings have been
> addressed,

I'm just trying to squash the gazillion warnings in auctex/style.  Those
are all free-vars and unresolved function warnings that will be ok at
runtime (style files can assume auctex is loaded, so they don't need to
require any auctex core files).

I've thought a simple fix would be to add a file local variable section
like this:

;; Local Variables:
;; byte-compile-warnings: (free-vars unresolved)
;; End:

That does indeed stop the unresolved function warnings but not the
free-vars warnings.  Why not?

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Glenn Morris]

Tassilo Horn wrote:

> ;; Local Variables:
> ;; byte-compile-warnings: (free-vars unresolved)
> ;; End:
>
> That does indeed stop the unresolved function warnings but not the
> free-vars warnings.  Why not?

Personally I think this is bad practice.

Anyway, aren't you missing a "not":

   byte-compile-warnings: (not free-vars unresolved)

?

Note that this only works since Emacs 23.1.
In older Emacs it will at best have precisely the opposite effect to the
one you intend.

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

Glenn Morris <rgm@gnu.org> writes:

Hi Glenn,

>> ;; Local Variables:
>> ;; byte-compile-warnings: (free-vars unresolved)
>> ;; End:
>>
>> That does indeed stop the unresolved function warnings but not the
>> free-vars warnings.  Why not?
>
> Personally I think this is bad practice.

Why?  As said, all those style files use LaTeX-* and TeX-* vars and
functions defined by AUCTeX's core.  However, the style files can't be
required individually, but AUCTeX itself loads them dynamically
depending on the \usepackages and \documentclass you use in your LaTeX
document.  And then it's evident that those vars/functions are defined.

> Anyway, aren't you missing a "not":
>
>    byte-compile-warnings: (not free-vars unresolved)
>
> ?

Arg, indeed. :-)

> Note that this only works since Emacs 23.1.  In older Emacs it will at
> best have precisely the opposite effect to the one you intend.

Well, AUCTeX releases have a (setq byte-compile-warnings nil) in a
custom lpath.el that's used when byte-compiling anyway.  My intent is
only to get rid of warnings that are actually ok just for the ELPA
builds.

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Glenn Morris]

Tassilo Horn wrote:

>> Personally I think this is bad practice.
>
> Why? 

Well, what if you make a typo and use a function that is really undefined?

> As said, all those style files use LaTeX-* and TeX-* vars and
> functions defined by AUCTeX's core.  However, the style files can't be
> required individually, but AUCTeX itself loads them dynamically
> depending on the \usepackages and \documentclass you use in your LaTeX
> document. 

Why can't the style files require whatever AUCTeX files they need?

> Well, AUCTeX releases have a (setq byte-compile-warnings nil) in a
> custom lpath.el that's used when byte-compiling anyway.

Which makes this whole exercise rather laughable, doesn't it?

"All releases must ship with no warnings."
<Disables warnings>
"Job done!"

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

Glenn Morris <rgm@gnu.org> writes:

>>> Personally I think this is bad practice.
>>
>> Why? 
>
> Well, what if you make a typo and use a function that is really
> undefined?

It'll throw at runtime, but hopefully it does so before shipping a
release.

>> As said, all those style files use LaTeX-* and TeX-* vars and
>> functions defined by AUCTeX's core.  However, the style files can't
>> be required individually, but AUCTeX itself loads them dynamically
>> depending on the \usepackages and \documentclass you use in your
>> LaTeX document.
>
> Why can't the style files require whatever AUCTeX files they need?

They could, I guess.  However, style files should be easy to write for
non-elisp experts.  They usually are nothing more than:

--8<---------------cut here---------------start------------->8---
(TeX-add-style-hook
 "<yourpackage-here>"
 (lambda ()
   (TeX-add-symbols
    '("<your-first-macro-here>" 1)  ;has one arg
    '("<your-2nd-macro-here>" 2)))) ;has two args
--8<---------------cut here---------------end--------------->8---

So that would need a (require 'tex), if it would also define latex
environments, it'll need (require 'latex) too, and if it'd also fiddles
with font-locking, it'll also (require 'font-latex).  I mean, we could
document in the manual section about writing custom style files which
AUCTeX files need to be required when using which function.  But style
files are usually written in parallel to working on/testing with a
sample tex document using the corresponding LaTeX style, so then the
functions/vars are defined anyway and one can just TAB your way through.

Another thing is that the style files reside in a subdirectory, so to
make the requires working their compilation would need a different
load-path.  (No big thing for the regular Makefile build job, but I'm
not sure about ELPA...)

And possibly adding requires would slow down the compilation process
quite a bit.  There are currently 144 style files.  As said, most of
them are rather short, but the tex, latex, and font-latex they'd need to
require are large (~14000 LOC in total).

>> Well, AUCTeX releases have a (setq byte-compile-warnings nil) in a
>> custom lpath.el that's used when byte-compiling anyway.
>
> Which makes this whole exercise rather laughable, doesn't it?

Kinda.  I didn't notice that before this bug report, too.  And I'll to
address the relevant warnings and remove that config.

> "All releases must ship with no warnings."
> <Disables warnings>
> "Job done!"

vc-annotate says:

  73660122 (Per Abrahamsen                 1996-08-29 20:32:16 +0000 6)

Good job, Per!  And it lasted for almost 18 years now.  ;-)

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Mosè Giordano]

2014-01-30 Tassilo Horn <tsdh@gnu.org>:
> And possibly adding requires would slow down the compilation process
> quite a bit.  There are currently 144 style files.  As said, most of
> them are rather short, but the tex, latex, and font-latex they'd need to
> require are large (~14000 LOC in total).

Is it possible to load `tex.el', `latex.el', and `font-latex.el' just
once through command line before compiling all style files instead of
adding a `require' in each file?

Bye,
Mosè

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

Tassilo Horn <tsdh@gnu.org> writes:

>> Why can't the style files require whatever AUCTeX files they need?
>
> They could, I guess.

I was wrong.  I've just added the needed requires to all style files,
but I get exactly as many warnings as before.  This is because of these
reasons.

1. Many TeX-* and LaTeX-* functions and variables are not generated
   before tex.el and latex.el are loaded.  AUCTeX has an auto parser
   facility that generates a parser for some kind of LaTeX thingy.
   Typical "thingies" in LaTeX are symbols/macros, environments,
   lengths, counters, or labels.  For each such thingy, functions and
   variables named TeX-thingy-* or LaTeX-thingy-* are generated.  E.g.,
   tex.el itself does

     (TeX-auto-add-type "symbol" "TeX")

   which generates functions/vars TeX-symbol-list,
   TeX-symbol-list-filtered, TeX-symbol-changed, etc.  (And the same for
   10 other thingies.)

   The byte-compiler doesn't seem to execute top-level funcalls, so all
   those functions/vars are unknown at compile-time.

2. The AUCTeX's auto parser is open to be used for style-files, too.
   For example, style/acronym.el does

     (TeX-auto-add-type "acronym" "LaTeX")

   which when evaluated creates LaTeX-acronym-list, etc.  Again, those
   are unknown to the byte-compiler.

I guess I should wrap those TeX-auto-add-type calls with a
`eval-when-compile', right?

3. How should one deal with code like this?

      (when (featurep 'font-latex)
        (font-latex-add-keywords ...))

4. Or with code like this?

      (defun foo ()
        (require 'url-util)
        (url-util-* ...))

Thanks,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

Mosè Giordano <giordano.mose@libero.it> writes:

>> And possibly adding requires would slow down the compilation process
>> quite a bit.  There are currently 144 style files.  As said, most of
>> them are rather short, but the tex, latex, and font-latex they'd need
>> to require are large (~14000 LOC in total).
>
> Is it possible to load `tex.el', `latex.el', and `font-latex.el' just
> once through command line before compiling all style files instead of
> adding a `require' in each file?

Our Makefile does just one emacs -f batch-byte-compile call passing all
*.el files as arguments, so even with many requires, each file will be
parsed only once.  And with the ELPA builds, I think it's the same
thing.

So my argument is not substantial.

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Stefan Monnier]

> And with the ELPA builds, I think it's the same thing.

IIRC there are different cases.

When installing an ELPA package, indeed all the .el files are compiled
within the running Emacs.  There aren't many guarantees of ordering tho,
so it could potentially happen that the style files get compiled before
loading tex.el.

When installing the whole GNU ELPA branch via "git clone .../elpa;
make", then each file is compiled individually in a separate Emacs
process.  But IIRC only the files in the top-level directory of each
package are byte-compiled in that case, so the style files won't be
byte-compiled at all.


        Stefan

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

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

>> And with the ELPA builds, I think it's the same thing.
>
> IIRC there are different cases.
>
> When installing an ELPA package, indeed all the .el files are compiled
> within the running Emacs.  There aren't many guarantees of ordering
> tho, so it could potentially happen that the style files get compiled
> before loading tex.el.

Ok, I see.

> When installing the whole GNU ELPA branch via "git clone .../elpa;
> make", then each file is compiled individually in a separate Emacs
> process.  But IIRC only the files in the top-level directory of each
> package are byte-compiled in that case, so the style files won't be
> byte-compiled at all.

That's ok.  But if the style files were compiled, adding the requires
into the style files would make the compilation take minutes, because
each style file compilation would need to load the core files first.

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Stefan Monnier]

> That's ok.  But if the style files were compiled, adding the requires
> into the style files would make the compilation take minutes, because
> each style file compilation would need to load the core files first.

Yup.  I personally don't see much need to add the `require's in those
style files.  Then again, I'm not too bothered by lingering warnings.


        Stefan

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

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

>> That's ok.  But if the style files were compiled, adding the requires
>> into the style files would make the compilation take minutes, because
>> each style file compilation would need to load the core files first.
>
> Yup.  I personally don't see much need to add the `require's in those
> style files.  Then again, I'm not too bothered by lingering warnings.

The problem is that the mass of warnings makes it hard to spot warnings
that are really defects.

However, now I've seen that adding requires to the style files doesnt't
help in the case where one style files uses vars/funs from another style
file (e.g., there's pstricks.el and several other sub-styles that use
funs/vars from the former, because they can assume that it's loaded
beforehand).  But style files can't be required cause they don't provide
a feature...

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Stefan Monnier]

> 1. Many TeX-* and LaTeX-* functions and variables are not generated
>    before tex.el and latex.el are loaded.  AUCTeX has an auto parser
[...]
>    The byte-compiler doesn't seem to execute top-level funcalls, so all
>    those functions/vars are unknown at compile-time.

Indeed, the byte-compiler compiles the code, rather than executes it.

But if it sees a (require 'foo) it will run that (require 'foo), i.e. it
will load foo.el(c), which executes all of the code in there.
So a (require 'tex) will execute (TeX-auto-add-type "symbol" "TeX") at
compile-time, and will hence cause TeX-symbol-list to exist at compile-time.

>      (TeX-auto-add-type "acronym" "LaTeX")
[...]
> I guess I should wrap those TeX-auto-add-type calls with a
> `eval-when-compile', right?

You could.  Or you could turn them into macros.

> 3. How should one deal with code like this?
>       (when (featurep 'font-latex)
>         (font-latex-add-keywords ...))

    (when (fboundp 'font-latex-add-keywords)
      (font-latex-add-keywords ...))

> 4. Or with code like this?
>
>       (defun foo ()
>         (require 'url-util)
>         (url-util-* ...))

Good question.  We usually use `declare-function' for these, but
admittedly, it's not a great solution.


        Stefan

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

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

>> 1. Many TeX-* and LaTeX-* functions and variables are not generated
>>    before tex.el and latex.el are loaded.  AUCTeX has an auto parser
> [...]
>>    The byte-compiler doesn't seem to execute top-level funcalls, so all
>>    those functions/vars are unknown at compile-time.
>
> Indeed, the byte-compiler compiles the code, rather than executes it.
>
> But if it sees a (require 'foo) it will run that (require 'foo),
> i.e. it will load foo.el(c), which executes all of the code in there.
> So a (require 'tex) will execute (TeX-auto-add-type "symbol" "TeX") at
> compile-time, and will hence cause TeX-symbol-list to exist at
> compile-time.

Ah, ok, but that doesn't help when foo.el does (TeX-auto-add-type "foo"
"TeX") and uses the generated functions itself, like it's done by
tex.el, latex.el, and all style files that define their own auto
parsers.  Concretely, I still get warnings if tex.el uses
(TeX-symbol-list) generated by (TeX-auto-add-type "symbol" "TeX"), but
if latex uses the same function, it's ok for the compiler.

>>      (TeX-auto-add-type "acronym" "LaTeX")
> [...]
>> I guess I should wrap those TeX-auto-add-type calls with a
>> `eval-when-compile', right?
>
> You could.

No, I get a compile error in tex.el when compiling

(defun TeX-auto-add-type (...) ...)
...
(eval-when-compile
  (TeX-auto-add-type "symbol" "TeX"))

because then TeX-auto-add-type is not known at compile-time.  So then
I'd need to wrap the defun, too, and also the function and variables
that are used in TeX-auto-add-type.  That doesn't seem manageable...

And if I wrap, e.g., the (TeX-auto-add-type "environment" "LaTeX") with
eval-with-compile, it compiles fine (cause it's in latex.el which
requires tex.el) and I get rid of some free-vars and unresolved
warnings, but then I get an error when finding a latex document.

  Debugger entered--Lisp error: (void-function LaTeX-add-environments-auto)

Wrapping with (eval-when (compile load eval) ...) seems to work, but I'm
not sure if that's a good idea.

> Or you could turn them into macros.

Indeed, that looks like a typical use-case for macros, but I'm rather
sure that there's a good reason that the auto parser stuff is like it
is.  David?

>> 3. How should one deal with code like this?
>>       (when (featurep 'font-latex)
>>         (font-latex-add-keywords ...))
>
>     (when (fboundp 'font-latex-add-keywords)
>       (font-latex-add-keywords ...))

While we are at it: David, is there any reason why somebody would want
to set TeX-install-font-lock to 'ignore nowadays so that font-latex is
not loaded?

If not, I'm tempted to remove the variable, require font-latex in
tex.el, and get rid of all those boundness checks in the styles.

>> 4. Or with code like this?
>>
>>       (defun foo ()
>>         (require 'url-util)
>>         (url-util-* ...))
>
> Good question.  We usually use `declare-function' for these, but
> admittedly, it's not a great solution.

I see.  The reason for the code above is that foo is only callable in
very special conditions.  Concretely, there're some functions that are
only used with recent GNU emacs version with dbus support and the user
using Evince as pdf viewer.

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[David Kastrup]

Tassilo Horn <tsdh@gnu.org> writes:

> Wrapping with (eval-when (compile load eval) ...) seems to work, but I'm
> not sure if that's a good idea.
>
>> Or you could turn them into macros.
>
> Indeed, that looks like a typical use-case for macros, but I'm rather
> sure that there's a good reason that the auto parser stuff is like it
> is.  David?

Sorry to disappoint you here, but that stuff was there well before me
and I've not messed with it to any noticeable degree.  I seem to
remember that Reiner Steib might have done a bit more in that respect,
but I might be mixing up names here, too.

At any rate, the base of the style code has probably not been touched
for something like 20 years, so it's quite likely that the reasons for
making any particular technical decision in that area are decidedly
historical.

> While we are at it: David, is there any reason why somebody would want
> to set TeX-install-font-lock to 'ignore nowadays so that font-latex is
> not loaded?

font-latex has different font highlighting from the Emacs default modes,
and some may prefer the latter (which also tends to track Emacs' current
capabilities better and might be more efficient for that reason).

-- 
David Kastrup

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

David Kastrup <dak@gnu.org> writes:

>>> Or you could turn them into macros.
>>
>> Indeed, that looks like a typical use-case for macros, but I'm rather
>> sure that there's a good reason that the auto parser stuff is like it
>> is.  David?
>
> [...]
> At any rate, the base of the style code has probably not been touched
> for something like 20 years, so it's quite likely that the reasons for
> making any particular technical decision in that area are decidedly
> historical.

Ok.  I've now turned TeX-auto-add-type into a macro and it seems to
work.  And it also uncovered a bug where the lambda added to
TeX-remove-style-hook contained (setq "[La]TeX-<type>-list" nil), i.e.,
there's a string rather a symbol.

I'll have to do some more testing before merging my local branch into
master and pushing, though.

>> While we are at it: David, is there any reason why somebody would
>> want to set TeX-install-font-lock to 'ignore nowadays so that
>> font-latex is not loaded?
>
> font-latex has different font highlighting from the Emacs default
> modes, and some may prefer the latter (which also tends to track
> Emacs' current capabilities better and might be more efficient for
> that reason).

Ok, thanks.

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Stefan Monnier]

>>> I guess I should wrap those TeX-auto-add-type calls with a
>>> `eval-when-compile', right?
>> You could.
> No, I get a compile error in tex.el when compiling

Of course, eval-when-compile and eval-and-compile come with their own
set of problems.  My "you could" wasn't really meant as an encouragement.

>> Or you could turn them into macros.
> Indeed, that looks like a typical use-case for macros, but I'm rather
> sure that there's a good reason that the auto parser stuff is like it
> is.  David?

Whatever the reason, looking at the code of TeX-auto-add-type, I think
it *really* should be turned into a macro, and use defvar/defalias
instead of set/fset.

> While we are at it: David, is there any reason why somebody would want
> to set TeX-install-font-lock to 'ignore nowadays so that font-latex is
> not loaded?

Would that make AUCTeX use tex-mode.el's font-lock rules?

>> Good question.  We usually use `declare-function' for these, but
>> admittedly, it's not a great solution.
> I see.  The reason for the code above is that foo is only callable in
> very special conditions.

That's what I expected.  We also have such code in various parts
of Emacs.  But we don't have a really good solution w.r.t to silencing
those warnings.

One potential solution I haven't investigated is to create a new
`require-autoload' which behaves somewhat like `require' (when
interpreted) but which the compiler would replace by a bunch of
autoloads (auto-generated by the compiler by taking the intersection of
the functions provided by the `require' and the functions called in the
file).  So you'd replace that code with

   (require-autoload 'url-util)
   (defun foo ()
     (url-util-* ...))

and url-util would only be loaded once you call `foo'.
Maybe `require-lazy' would be a better name for it, but in any case as
long as it's not implemented, its name doesn't matter much.


        Stefan

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

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

>>> Or you could turn them into macros.
>> Indeed, that looks like a typical use-case for macros, but I'm rather
>> sure that there's a good reason that the auto parser stuff is like it
>> is.  David?
>
> Whatever the reason, looking at the code of TeX-auto-add-type, I think
> it *really* should be turned into a macro, and use defvar/defalias
> instead of set/fset.

Yes, I've done that now in a local branch.  Seems to be the way to go,
but I need to do some more testing before pushing out that change.

>> While we are at it: David, is there any reason why somebody would
>> want to set TeX-install-font-lock to 'ignore nowadays so that
>> font-latex is not loaded?
>
> Would that make AUCTeX use tex-mode.el's font-lock rules?

TeX-install-font-lock has 3 possible values.  font-latex-setup uses
AUCTeX's rules, tex-font-setup uses tex-mode's rules, and ignore doesn't
set up any font-lock rules.  (So my question was a bit misleading.)

font-latex has some nice goodies like being able to add custom
font-locking rules for your own macros/environments very easily.

> Maybe `require-lazy' would be a better name for it, but in any case as
> long as it's not implemented, its name doesn't matter much.

Yup.

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Glenn Morris]

Tassilo Horn wrote:

> (but no declare-functions cause that's not available on older
> emacsen/xemacs)

It's available since Emacs 22.2, ie 6 years, or the past 9 Emacs releases.
If XEmacs has not added even a compat stub in that time, which would
take about a minute, that seems telling.

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Thierry Volpiatto]

Glenn Morris <rgm@gnu.org> writes:

> Tassilo Horn wrote:
>
>> (but no declare-functions cause that's not available on older
>> emacsen/xemacs)
>
> It's available since Emacs 22.2, ie 6 years, or the past 9 Emacs releases.
> If XEmacs has not added even a compat stub in that time, which would
> take about a minute, that seems telling.

While you are at it, I had often complaints about some completing-read's
working badly with helm.
This is because they are not written correctly in Auctex.
I have submitted a bug long time ago but never had an answer.
If you are interested to fix this you can have a look here:

https://github.com/thierryvolpiatto/auctex

-- 
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

Glenn Morris <rgm@gnu.org> writes:

>> (but no declare-functions cause that's not available on older
>> emacsen/xemacs)
>
> It's available since Emacs 22.2, ie 6 years, or the past 9 Emacs releases.
> If XEmacs has not added even a compat stub in that time, which would
> take about a minute, that seems telling.

I've just checked XEmacs 21.5_beta33, and no, it's not there.  And it
wouldn't matter much since AUCTeX tries to support at least the latest
released XEmacs version which is 21.4.  (Actually, I'm not really trying
hard to achieve that actively, but I try not to break that support
carelessly.)

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:

Hi Thierry,

> While you are at it, I had often complaints about some completing-read's
> working badly with helm.
> This is because they are not written correctly in Auctex.
> I have submitted a bug long time ago but never had an answer.

Oh, sorry, I must have missed it.

> If you are interested to fix this you can have a look here:
>
> https://github.com/thierryvolpiatto/auctex

Fixed, thanks!

Bye,
Tassilo

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Thierry Volpiatto]

Tassilo Horn <tsdh@gnu.org> writes:

> Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
>
> Hi Thierry,
>
>> While you are at it, I had often complaints about some completing-read's
>> working badly with helm.
>> This is because they are not written correctly in Auctex.
>> I have submitted a bug long time ago but never had an answer.
>
> Oh, sorry, I must have missed it.
>
>> If you are interested to fix this you can have a look here:
>>
>> https://github.com/thierryvolpiatto/auctex
>
> Fixed, thanks!

Great! I will remove my branch.

> Bye,
> Tassilo

-- 
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Stefan Kangas]

Neil Jackson <neil.jackson@live.ca> writes:

> Observed behaviour:
> On updating to latest Auctex from the Package Manager, there were
> hundreds of warnings during compilation.
>
> Expected behaviour:
> Packages in Elpa compile without warnings.

I tried installing auctex from GNU ELPA using current master.  I still
see many few warnings about obsolete functions and free variables, but
not hundreds.  Perhaps a couple of dozen.

Best regards,
Stefan Kangas

bug#16573: 24.3; Auctex (11.87.2) in Elpa issues hundreds of warnings on compile

[Tassilo Horn]

I'm closing this issue given its age, and the current AUCTeX version
issues almost no byte-compile warnings anymore.