bug#69000: Error while upgrading
Hi Michael On Sat, 10 Feb 2024 at 15:29, Michael Heerdegen via bug-auctex via Bug reporting list for AUCTeX wrote: > As expected it's fixed for me as well. Thanks to everyone. Thanks for confirming it, I'm closing the ticket. > Note 2: I did not find information about how to report bugs in the > AucTex manual. Either I missed it or it should maybe be added. I think it's the former case, the instructions about how to report bugs are at the very beginning of the AUCTeX manual: https://www.gnu.org/software/auctex/manual/auctex/index.html > Bug reports should go to bug-auctex@gnu.org, suggestions for new features, > and pleas for help should go to either auctex-de...@gnu.org (the AUCTeX > developers), or to auc...@gnu.org if they might have general interest. Please > use the command M-x TeX-submit-bug-report to report bugs if possible. > You can subscribe to a low-volume announcement list by sending “subscribe” in > the subject of a mail to info-auctex-requ...@gnu.org. Best, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#51239: emptyish web page found via google 'auctex emacs'
Dear Keita, On Sat, 16 Oct 2021 at 17:22, Ikumi Keita wrote: > > Hi Mosè, > > >>>>> Mosè Giordano writes: > > that's how texi2html works, I don't think we can do much about that. > > It seems that texi2html was declared as obsolete a decade ago and the > developer recommends to switch to makeinfo[1]. Maybe we should consider > to switch and seek for a way to generate less emptyish html pages by > makeinfo. > > [1] https://www.nongnu.org/texi2html/ > > At least the current doc/Makefile generates such pages by makeinfo when > I issue "make html/index.html" in doc directory. (makeinfo is chosen by > Makefile when texi2html is missing and makeinfo is available.) You have to build with something like "make www-doc TAG=12.3". It looks like that adapting the workflow to makeinfo would require quite some work and I'm not even sure that anything will change at all with regard to splitting. Maybe the only thing one could do is to add some text to section "1.3.1 Functions for editing TeX files" to not have it completely empty? But still, there is technically not much wrong, it's that that section is really empty and users need to press the next button to read the next section. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#51239: emptyish web page found via google 'auctex emacs'
Hi Bruce, that's how texi2html works, I don't think we can do much about that. You may want to read the "all-in-one-page" manual instead the one "split-into-every-single-possibly-empty-section": https://www.gnu.org/software/auctex/manual/auctex.html#Editing-Facilities Bye, Mosè On Sat, 16 Oct 2021 at 15:41, bruce robertson wrote: > > https://www.gnu.org/software/auctex/manual/auctex/Editing-Facilities.html#Editing-Facilities > is pretty much empty whereas > https://www.gnu.org/software/auctex/manual/auctex/Editing.html#Editing > seems to be useful > > > -- > λέγει αὐτῷ Ἰησοῦς Ἐγώ εἰμι ἡ ὁδὸς καὶ ἡ ἀλήθεια καὶ ἡ ζωή· οὐδεὶς ἔρχεται > πρὸς τὸν Πατέρα εἰ μὴ δι' ἐμοῦ. ΚΑΤΑ ΙΩΑΝΝΗΝ > ___ > bug-auctex mailing list > bug-auctex@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-auctex ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#44609: 12.3.1; auctex.el does not (provide 'auctex), which breaks use-package
On Fri, 13 Nov 2020 at 11:34, Vladimir Nikishkin wrote: > > Well, how would I know that? It's that documented anywhere? I showed you it's a notable example in `use-package' documentation. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#44609: 12.3.1; auctex.el does not (provide 'auctex), which breaks use-package
On Fri, 13 Nov 2020 at 10:20, Vladimir Nikishkin wrote: > > I do not see how this is connected to the bug report. I'm not installing the > tex package. The connection you're missing is that `tex' is the name of the feature provided by AUCTeX: http://git.savannah.gnu.org/cgit/auctex.git/tree/tex.el?id=3982971f7efa2db9275b1470fcd17d1d9f285f6e#n6731. That's also the name of the feature you want to use to ensure `auctex-latemk' is loaded after AUCTeX. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#44609: 12.3.1; auctex.el does not (provide 'auctex), which breaks use-package
Hi Vladimir,
did you read the README.md of `use-package'? It actually has an
example about AUCTeX:
https://github.com/jwiegley/use-package/blob/caa92f1d64fc25480551757d854b4b49981dfa6b/README.md#package-installation
> If you need to install a different package from the one named by use-package,
> you can specify it like this:
(use-package tex
:ensure auctex)
Bye,
Mosè
On Fri, 13 Nov 2020 at 02:09, Vladimir Nikishkin wrote:
>
>
> Dear AUCTeX developers.
> I am using use-package to keep the init.el decently structured.
> It is typical for package files to (provide) a feature that has the same
> name as the name of the package itself.
> For example, it helps with dependency tracking.
>
> E.g. you would say "Only load auctex-latexmk after 'auctex has been
> loaded".
> Could something like `(provide 'auctex)' be added to the auctex.el?
>
> Yours sincerely,
> Vladimir
>
> Emacs : GNU Emacs 27.1 (build 1, x86_64-slackware-linux-gnu, GTK+ Version
> 3.24.22)
> of 2020-08-12
> Package: 12.3.1
>
> current state:
> ==
> (setq
> AUCTeX-date "2020-10-22"
> window-system 'x
> LaTeX-version "2e"
> TeX-style-path '("~/.emacs.d/auctex"
> "/home/lockywolf/.emacs.d/elpa/auctex-12.3.1/style"
> "/home/lockywolf/.emacs.d/auctex/auto"
> "/home/lockywolf/.emacs.d/auctex/style" "auto" "style")
> TeX-auto-save nil
> TeX-parse-self nil
> TeX-master t
> TeX-command-list '(("LatexMk" "latexmk %(-PDF)%S%(mode) %(file-line-error)
> %(extraopts) %t"
> TeX-run-latexmk nil (plain-tex-mode latex-mode
> doctex-mode) :help
> "Run LatexMk")
> ("TeX"
> "%(PDF)%(tex) %(file-line-error) %`%(extraopts)
> %S%(PDFout)%(mode)%' %t"
> TeX-run-TeX nil (plain-tex-mode ams-tex-mode
> texinfo-mode) :help
> "Run plain TeX")
> ("LaTeX" "%`%l%(mode)%' %T" TeX-run-TeX nil (latex-mode
> doctex-mode)
> :help "Run LaTeX")
> ("Makeinfo" "makeinfo %(extraopts) %t" TeX-run-compile nil
> (texinfo-mode) :help "Run Makeinfo with Info output")
> ("Makeinfo HTML" "makeinfo %(extraopts) --html %t"
> TeX-run-compile nil
> (texinfo-mode) :help "Run Makeinfo with HTML output")
> ("AmSTeX" "amstex %(PDFout) %`%(extraopts) %S%(mode)%'
> %t" TeX-run-TeX
> nil (ams-tex-mode) :help "Run AMSTeX")
> ("ConTeXt" "%(cntxcom) --once --texutil %(extraopts)
> %(execopts)%t"
> TeX-run-TeX nil (context-mode) :help "Run ConTeXt once")
> ("ConTeXt Full" "%(cntxcom) %(extraopts) %(execopts)%t"
> TeX-run-TeX nil
> (context-mode) :help "Run ConTeXt until completion")
> ("BibTeX" "bibtex %s" TeX-run-BibTeX nil
> (plain-tex-mode latex-mode doctex-mode ams-tex-mode
> texinfo-mode
> context-mode)
> :help "Run BibTeX")
> ("Biber" "biber %s" TeX-run-Biber nil
> (plain-tex-mode latex-mode doctex-mode ams-tex-mode
> texinfo-mode) :help
> "Run Biber")
> ("View" "%V" TeX-run-discard-or-function t t :help "Run
> Viewer")
> ("Print" "%p" TeX-run-command t t :help "Print the file")
> ("Queue" "%q" TeX-run-background nil t :help "View the
> printer queue"
> :visible TeX-queue-command)
> ("File" "%(o?)dvips %d -o %f " TeX-run-dvips t
> (plain-tex-mode latex-mode doctex-mode ams-tex-mode
> texinfo-mode) :help
> "Generate PostScript file")
> ("Dvips" "%(o?)dvips %d -o %f " TeX-run-dvips nil
> (plain-tex-mode latex-mode doctex-mode ams-tex-mode
> texinfo-mode) :help
> "Convert DVI file to PostScript")
> ("Dvipdfmx" "dvipdfmx %d" TeX-run-dvipdfmx nil
> (plain-tex-mode latex-mode doctex-mode ams-tex-mode
> texinfo-mode) :help
> "Convert DVI file to PDF with dvipdfmx")
> ("Ps2pdf" "ps2pdf %f" TeX-run-ps2pdf nil
> (plain-tex-mode latex-mode doctex-mode ams-tex-mode
> texinfo-mode) :help
> "Convert PostScript file to PDF")
> ("Glossaries" "makeglossaries %s" TeX-run-command nil
> (plain-tex-mode latex-mode doctex-mode ams-tex-mode
> texinfo-mode) :help
> "Run makeglossaries to create glossary\n file")
> ("Index" "makeindex %s" TeX-run-index nil
> (plain-tex-mode latex-mode doctex-mode ams-tex-mode
> texinfo-mode) :help
> "Run makeindex to create index file")
>
bug#37124: Lisp snippet for TeX-electric-math in manual
Hi Arash,
On Tue, 20 Aug 2019 at 22:57, Arash Esbati wrote:
>
> Hi all,
>
> there is a lisp snippet in the manual for `TeX-electric-math'[1]:
>
> (add-hook 'plain-TeX-mode-hook
> (lambda () (set (make-variable-buffer-local 'TeX-electric-math)
> (cons "$" "$"
> (add-hook 'LaTeX-mode-hook
> (lambda () (set (make-variable-buffer-local 'TeX-electric-math)
> (cons "\\(" "\\)"
>
> `make-variable-buffer-local' seems wrong to me, I think
> `make-local-variable' is the intended function.
I think you're correct.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#35363: 12.1.2; Generation of previews fails under Windows 10
On Mon, 29 Apr 2019 at 13:45, Ikumi Keita wrote: > So I think that it would > be worth asking the MiKTeX author to do so. Don't expect quick response though: https://sourceforge.net/p/miktex/bugs/2310/ ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24079: 11.89.4; Auctex noweb issue.
Dear all, this bug should have been fixed in ESS: https://github.com/emacs-ess/ESS/issues/354 Bye, Mosè On Fri, Jul 29, 2016 at 12:32 AM Mosè Giordano wrote: > > Hi Reinhard, > > 2016-07-28 23:52 GMT+02:00 Reinhard Kotucha : > > On 2016-07-28 at 18:24:56 +0200, Mosè Giordano wrote: > > > > > but when I `edebug' it the problem goes away. > > > > It seems that you encountered a Heisenbug. > > > > https://en.wikipedia.org/wiki/Heisenbug > > Yes, I know, indeed I linked the same Wikipedia article in the ESS bug > ticket ;-) > > > If so, edebug is probably not the best choice. > > Ok, but how to debug then? I noticed that if I press C-g repeatedly > only the first line is uncommented, the others remain commented, so > the infinite loop must lies somewhere between the first and the second > deletion of the comment string, but I can't discover where exactly. > > Bye, > Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#28905: 11.90.2.2017-07-25; TeX-documentation-texdoc blocks
Hi Keita, On Sun, Nov 4, 2018 at 10:48 AM Ikumi Keita wrote: > > Hi Fran and all, > > > "Fran Burstall (Gmail)" writes: > > Hi Ikumi, > > It works for me. Pass "amsmath" to the patched TeX-documentation-texdoc > > and it fires evince on the documentation without blocking emacs; fire it on > > "foobar" and I get a sensible message about not finding any documentation. > > Thanks for confirmation. It works just as expectedly. How about you, > Mosè? I didn't try the patch, just read it. The idea should be to launch an asynchronous process and show its output, correct? That should be the way to go. Only one comment: is it necessary to use `start-process-shell-command'? Wouldn't `start-process' be sufficient? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30861: 12.1.0; process-kill-without-query removed from emacs, still used in preview.el
Hi Pavel, 2018-03-19 20:29 GMT+01:00 Pavel Zorin-Kranich : > According to > http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=f1c48b0 > the function process-kill-without-query has been removed from emacs but > it is still used by preview.el > > Running preview on any latex file results (after some tex output) in the > error > > PDF2DSC sentinel: Symbol’s function definition is void: > process-kill-without-query This is already fixed in the development version of AUCTeX with commit * b292942e (2018-01-17) Remove some obsolete functions (https://git.savannah.gnu.org/cgit/auctex.git/commit/?id=b292942e2a2edfaf14b8ca351dee6db2f89a0a94). I guess we may want to make a new ELPA release at this point. Tassilo, could you please take care of this? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30640: [patch] replace last cl
2018-03-01 16:43 GMT+01:00 Alex Branham : > Whoops! I didn't think about checking the other files for cl functions. > Since this removes the last cl function, the byte-compiler didn't know > about the cl functions anymore. There was one lurking in latex.el that > we must've missed before. Now make && make check is successful! Patch applied, thanks. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30640: [patch] replace last cl
Hi Alex, 2018-02-28 1:47 GMT+01:00 Alex Branham : > I think this takes case of the last (require 'cl) statement. thanks again for working on this! However, I can't compile AUCTeX with your patch: latex.el:6542:8:Error: Wrong type argument: sequencep, beg-col Could you please have a look at this? Thanks, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30484: Use lexical binding
Hi David, 2018-02-16 10:39 GMT+01:00 David Kastrup : > Mosè Giordano writes: > >> We should make sure AUCTeX doesn't fundamentally use dynamic binding, >> in order to later switch to lexical binding. > > You have to pick one or the other for the equivalent of closures. > > I do think we have a few cases of those that would benefit from lexical > binding. Should I go over them? Are you volunteering to fix this issue? If so, please go ahead :-) Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30423: separate flymake into latex-flymake.el
Hi Alex, 2018-02-16 17:57 GMT+01:00 Alex Branham : > Here's a different version of the patch I sent with flymake support in > its own file. I also removed the lexical-binding from latex.el. Great! Patch installed, thanks again. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30424: [patch] replace cl with cl-lib
Hi Alex, patch installed, thanks! 2018-02-16 16:05 GMT+01:00 Alex Branham : > Yes, that's right. I noticed a few comments like, "FIXME use cl-lib > instead of cl" when writing the flymake support and decided that it > would be a pretty easy fix for me to contribute. Good idea, I think those are cookies left by Stefan :-) Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30423: 2018-01-25; [patch] flymake support
Hi Alex, thanks again for your contribution. I think it's fine in principle to support Flymake, as long as this doesn't introduce dependence on external packages. We strive to keep dependencies as low as possible. 2018-02-11 19:06 GMT+01:00 Alex Branham : > Flymake got a major rewrite in Emacs 26, the attached patch adds support for > this in latex.el. Users can enable it by calling adding flymake-mode to > LaTeX-mode-hook. > > > > From 0b8eeebd01d0ed25823d4f40a7ab3cff0d150b8f Mon Sep 17 00:00:00 2001 > From: Alex Branham > Date: Sun, 11 Feb 2018 11:54:09 -0600 > Subject: [PATCH] Support flymake in Emacs 26+ using chktex > > --- > latex.el | 73 > +++- > 1 file changed, 72 insertions(+), 1 deletion(-) > > diff --git a/latex.el b/latex.el > index c2d8a4ca..e3792faf 100644 > --- a/latex.el > +++ b/latex.el > @@ -1,4 +1,4 @@ > -;;; latex.el --- Support for LaTeX documents. > +;;; latex.el --- Support for LaTeX documents. -*- lexical-binding: t; -*- I'm concerned by this change. We haven't used lexical binding so far because we used to support very old Emacsens. While this change may be desirable, I've the feeling that AUCTeX relies on dynamic binding. I've opened a ticket as a memo for anyone willing to work on it: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30484. Does your patch fundamentally rely on lexical binding or can work also with dynamic binding? In addition, I'm not sure latex.el is the right place for this. The file contains only stuff for editing LaTeX documents. For example, support for ispell is in its own module, required by latex.el. What other people thinks about this? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30484: Use lexical binding
We should make sure AUCTeX doesn't fundamentally use dynamic binding, in order to later switch to lexical binding. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30424: [patch] replace cl with cl-lib
Hi Alex,
thanks for this new patch. From what I've seen this doesn't introduce
runtime dependence on cl-lib but just replaces cl macros with
corresponding cl-lib macros, is this correct?
Bye,
Mosè
2018-02-11 19:10 GMT+01:00 Alex Branham :
> The attached patch replaces cl with cl-lib.
>
> From 6bc94eaee8a189af5f847878b6280c6a1a0e4b54 Mon Sep 17 00:00:00 2001
> From: Alex Branham
> Date: Tue, 30 Jan 2018 20:56:13 -0600
> Subject: [PATCH] Replace cl with cl-lib
>
> ---
> bib-cite.el| 5 +++--
> font-latex.el | 2 +-
> latex.el | 3 ++-
> style/babel.el | 3 ++-
> style/caption.el | 22 +++---
> style/empheq.el| 12 ++--
> style/enumitem.el | 18 +-
> style/floatrow.el | 17 +
> style/fvextra.el | 9 +
> style/listings.el | 11 ++-
> style/mdframed.el | 13 +++--
> style/tcolorbox.el | 7 ---
> 12 files changed, 65 insertions(+), 57 deletions(-)
>
> diff --git a/bib-cite.el b/bib-cite.el
> index 0be0eb0b..5cb8a1d2 100644
> --- a/bib-cite.el
> +++ b/bib-cite.el
> @@ -589,7 +589,8 @@
> ;;
>
> ;;; Code:
>
> -(eval-when-compile (require 'cl))
> +(eval-when-compile
> + (require 'cl-lib))
>
> (defgroup bib-cite nil
>"bib-cite, LaTeX minor-mode to display \\cite, \\ref and \\label commands."
> @@ -2427,7 +2428,7 @@ bib-dos-or-os2-variable affects:
> (or (and (fboundp 'TeX-split-string)
> (TeX-split-string sep-char value))
> (dired-split sep-char value)
> - (loop for x in entries if (bib-cite-file-directory-p x) collect x
> + (cl-loop for x in entries if (bib-cite-file-directory-p x) collect
> x
>
> (provide 'bib-cite)
> ;;; bib-cite.el ends here
> diff --git a/font-latex.el b/font-latex.el
> index 9b621985..1df751ad 100644
> --- a/font-latex.el
> +++ b/font-latex.el
> @@ -43,7 +43,7 @@
> (require 'tex)
>
> (eval-when-compile
> - (require 'cl))
> + (require 'cl-lib))
>
> (defgroup font-latex nil
>"Font-latex text highlighting package."
> diff --git a/latex.el b/latex.el
> index c2d8a4ca..05d6f55c 100644
> --- a/latex.el
> +++ b/latex.el
> @@ -31,7 +31,8 @@
> (require 'tex)
> (require 'tex-style)
> (require 'tex-ispell)
> -(eval-when-compile (require 'cl)) ;FIXME: Use cl-lib.
> +(eval-when-compile
> + (require 'cl-lib))
>
> ;;; Syntax
>
> diff --git a/style/babel.el b/style/babel.el
> index c1119b9b..d8c5e3ff 100644
> --- a/style/babel.el
> +++ b/style/babel.el
> @@ -30,7 +30,8 @@
>
> ;;; Code:
>
> -(eval-when-compile (require 'cl))
> +(eval-when-compile
> + (require 'cl-lib))
>
> (defvar LaTeX-babel-language-list
>'("afrikaans"
> diff --git a/style/caption.el b/style/caption.el
> index df6328e3..f23e59da 100644
> --- a/style/caption.el
> +++ b/style/caption.el
> @@ -34,8 +34,8 @@
>
> ;;; Code:
>
> -;; Needed for compiling `pushnew':
> -(eval-when-compile (require 'cl))
> +(eval-when-compile
> + (require 'cl-lib))
>
> ;; Needed for auto-parsing.
> (require 'tex)
> @@ -168,19 +168,19 @@ in `caption'-completions."
>;; For `\DeclareCaptionOption', only add the value
>;; (remember: key=^^, val="defined key")
>(if (string-equal key "option")
> - (pushnew (list val) opts :test #'equal)
> + (cl-pushnew (list val) opts :test #'equal)
> ;; For anything but `\DeclareCaptionOption', do the standard
> ;; procedure. Again, take care of `subrefformat' for `subcaption.el'.
> (if val-match
> (progn
> (when (and (string-equal key "labelformat")
> (boundp 'LaTeX-subcaption-key-val-options))
> - (pushnew (list "subrefformat"
> - (TeX-delete-duplicate-strings (apply #'append
> (list val) val-match)))
> -opts :test #'equal))
> - (pushnew (list key (TeX-delete-duplicate-strings (apply
> #'append (list val) val-match)))
> - opts :test #'equal))
> - (pushnew (list key (list val)) opts :test #'equal)))
> + (cl-pushnew (list "subrefformat"
> + (TeX-delete-duplicate-strings (apply
> #'append (list val) val-match)))
> + opts :test #'equal))
> + (cl-pushnew (list key (TeX-delete-duplicate-strings (apply
> #'append (list val) val-match)))
> + opts :test #'equal))
> + (cl-pushnew (list key (list val)) opts :test #'equal)))
>(setq LaTeX-caption-key-val-options-local (copy-alist opts
>;; Support for environments defined with newfloat.sty: These
>;; environments are added to "type" and "type*" key:
> @@ -192,8 +192,8 @@ in `caption'-completions."
> (val-match (cdr (assoc key LaTeX-caption-key-val-options-local)))
>
bug#30149: [Patch] remove some obsolete functions
Hi Alex, 2018-01-25 18:23 GMT+01:00 Alex Branham : > Helpful reminder email :-) Thank you so much for the remainder! I installed the patch. I only had to replace the path of preview.el, because that file is not tracked under git, there is preview.el.in instead. Thanks again for your contribution, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30239: Renaming environment "slide" to "frame"
Hi Agathe, 2018-01-24 19:10 GMT+01:00 Agathe Herrou : > Hello, > > When using AUCTeX with Beamer, the default environment when running C-c > C-e is "slide". As far as I know, this environment doesn't exist, and > the correct one is "frame". Attached is a suggested corrective. Thanks for your contribution, however there is no "slide" environment in our style file for beamer: https://git.savannah.gnu.org/cgit/auctex.git/tree/style/beamer.el Where did get that style file? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#30158: 11.90.2.2017-07-25; latex from command line is ok, but called from auctex, gives problems
Hi Uwe, 2018-01-20 14:19 GMT+01:00 Uwe Brauer : > So I now started emacs from the command line and then everything is > fine. Only when I use an icon to start with. Strange. This isn't much strange if you use Ubuntu. If I remember correctly, programs started from the desktop environment don't know about users init files. I never tried myself because I didn't need to, but you may want to have a look at https://github.com/purcell/exec-path-from-shell in order to set your environment variables from the shell. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#20781: Xemacs 21.4.22 MaC OS Yosmite: (customize-option 'TeX-view-program-list) fails with error
Dear Uwe,
I'm closing this ticket as we don't support XEmacs anymore.
Bye,
Mosè
2015-06-10 8:44 GMT+02:00 Uwe Brauer :
>
> Using Xemacs 21.4.22 mule on Mac OS Yosmite, I obtain the following
> error when trying to run
> (customize-option 'TeX-view-program-list) fails with error
> However
> (customize-option 'TeX-command-list)
>
> Works!!
>
> Uwe Brauer
>
>
> Debugger entered--Lisp error: (void-function nil)
> nil((alist :key-type (string :tag "Name") :value-type (choice (group :tag
> "Command" ...) (group :tag "Command parts" ...) (group :tag "Function"
> function))) (("okular" "okular -unique %o#src:%n%b")))
> widget-apply((alist :key-type (string :tag "Name") :value-type (choice
> (group :tag "Command" ...) (group :tag "Command parts" ...) (group :tag
> "Function" function))) :match (("okular" "okular -unique %o#src:%n%b")))
> custom-variable-value-create((custom-variable :custom-form edit :value
> TeX-view-program-list :tag "Tex View Program List" :custom-state unknown
> :documentation-shown t))
> widget-apply((custom-variable :custom-form edit :value
> TeX-view-program-list :tag "Tex View Program List" :custom-state unknown
> :documentation-shown t) :value-create)
> widget-default-create((custom-variable :custom-form edit :value
> TeX-view-program-list :tag "Tex View Program List" :custom-state unknown
> :documentation-shown t))
> widget-apply((custom-variable :custom-form edit :value
> TeX-view-program-list :tag "Tex View Program List" :custom-state unknown
> :documentation-shown t) :create)
> widget-create(custom-variable :documentation-shown t :custom-state unknown
> :tag "Tex View Program List" :value TeX-view-program-list)
> # :documentation-shown t :custom-state unknown :tag custom-unlispify-tag-name
> :value] 10>((TeX-view-program-list custom-variable))
> mapcar(# :documentation-shown t :custom-state unknown :tag custom-unlispify-tag-name
> :value] 10> ((TeX-view-program-list custom-variable)))
> custom-buffer-create-internal(((TeX-view-program-list custom-variable)) nil)
> custom-buffer-create(((TeX-view-program-list custom-variable)) "*Customize
> Variable: Tex View Program List*")
> # custom-variable format "*Customize Variable: %s*" custom-unlispify-tag-name]
> 6 ("/opt/local/lib/xemacs-21.4.22/lisp/cus-edit.elc" . 18275)
> (custom-variable-prompt)>(TeX-view-program-list)
> call-interactively(customize-option)
> command-execute(customize-option t)
> execute-extended-command(nil)
> call-interactively(execute-extended-command)
>
>
>
>
>
>
>
> Emacs : XEmacs 21.4 (patch 22) "Instant Classic" [Lucid]
> (i386-apple-darwin14.0.0, Mule) of Mon Nov 3 2014 on AroberiMac.local
> Package: 11.88
>
> current state:
> ==
> (setq
> AUCTeX-date "2014-10-29"
> window-system 'x
> LaTeX-version "2e"
> TeX-style-path '("/usr/local/var/auctex/"
> "/opt/local/lib/xemacs-21.4.22/xemacs-packages/etc/auctex/style"
> "/Users/arober/.emacs.d/auctex/auto"
> "/Users/arober/.emacs.d/auctex/style" "auto" "style")
> TeX-auto-save nil
> TeX-parse-self nil
> TeX-master t
> TeX-command-list '(("TeX" "%(PDF)%(tex) %(extraopts) %`%S%(PDFout)%(mode)%'
> %t" TeX-run-TeX nil
> (plain-tex-mode texinfo-mode ams-tex-mode) :help "Run
> plain TeX")
> ("LaTeX" "%`%l%(mode)%' %t" TeX-run-TeX t (latex-mode
> doctex-mode) :help "Run LaTeX")
> ("Makeinfo" "makeinfo %(extraopts) %t" TeX-run-compile
> nil (texinfo-mode) :help
> "Run Makeinfo with Info output")
> ("Makeinfo HTML" "makeinfo %(extraopts) --html %t"
> TeX-run-compile nil (texinfo-mode) :help
> "Run Makeinfo with HTML output")
> ("AmSTeX" "%(PDF)amstex %(extraopts)
> %`%S%(PDFout)%(mode)%' %t" TeX-run-TeX t (ams-tex-mode)
> :help "Run AMSTeX")
> ("ConTeXt" "texexec --once --texutil %(extraopts)
> %(execopts)%t" TeX-run-TeX nil
> (context-mode) :help "Run ConTeXt once")
> ("ConTeXt Full" "texexec %(extraopts) %(execopts)%t"
> TeX-run-TeX nil (context-mode) :help
> "Run ConTeXt until completion")
> ("BibTeX" "bibtex %s" TeX-run-BibTeX nil t :help "Run
> BibTeX")
> ("Biber" "biber %s" TeX-run-Biber nil t :help "Run Biber")
> ("pdflatex" "pdflatex %t" TeX-run-command t t)
> ("milatex" "latex -src-specials %t" TeX-run-command t t)
> ("mipdf" "dvips %d -o %f |ps2pdf %f" TeX-run-command t t)
> ("dvips" "dvips %d -o %f" TeX-run-command t t) ("ps2pdf"
> "ps2pdf %f" TeX-run-command t t)
> ("View" "%V" TeX-run-discard-or-function t t :help "Run
> Viewer")
> ("xdvi" "xdvi %d" TeX-run-command t t)
>
bug#30149: [Patch] incorrect patch sent
Hi Alex, thank you so much for your contribution, much appreciated! I see that you already signed copyright papers for Emacs, so there is no need to do it again for AUCTeX. I have only one question: 2018-01-17 20:45 GMT+01:00 Alex Branham : > diff --git a/tex.el b/tex.el > index 5ee02b4c..d9f680b6 100644 > --- a/tex.el > +++ b/tex.el > @@ -1358,9 +1358,7 @@ viewer." > (cond ((fboundp #'select-frame-set-input-focus) >(select-frame-set-input-focus (selected-frame))) > ((fboundp #'x-focus-frame) > - (x-focus-frame (selected-frame))) > - ((fboundp #'focus-frame) > - (focus-frame (selected-frame)) > + (x-focus-frame (selected-frame)) >(error "Couldn't find the %s instance for %s" (capitalize app) uri Why not directly using `select-frame-set-input-focus' instead of the `cond'? It should be always available in Emacs >= 24.1, or not? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#29525: Please don't default to "--unique" mode for Okular
2017-12-05 13:57 GMT+01:00 Reuben Thomas : >> I'm honestly lost. Could you please explain what's the workflow you'd >> like to use? I thought it's something like this: >> >> 1) edit the source in AUCTeX >> >> 2) compile it with C-c C-c >> >> 3) open the output document in Okular with C-c C-v >> >> 4) switch back to Emacs with the window manager (usually ALT + TAB, I >> guess) >> >> 5) edit again >> >> 6 compile again with C-c C-c >> >> 7) switch to Okular with the window manager. The document will >> auto-reload >> >> 8) reiterate from point 4 >> >> If this is your workflow, forward search can't be used --- C-c C-v is >> run only once at point 3 --- unless you close Okular all the time. > > > This is correct: I am not using forward search. My bug report is simply > about launching a viewer. My workflow is much simpler: I open the viewer > once, and after that I let it auto-refresh, changing position in the PDF > window using its own controls. Ok, then I'm against making the usage of forward search more uncomfortable by default. If Okular will ever get the ability to not open a new instance for an already open document --- and I really hope so --- the default can be safely changed. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#29525: Please don't default to "--unique" mode for Okular
2017-12-04 13:58 GMT+01:00 Reuben Thomas : >> I missed to stress one important point of C-c C-v > > > There seems to be some confusion here: you brought up C-c C-v; I didn't > mention it. I was just using the plain "View" command from the C-c C-c menu. > (I guess I should investigate forward search again, though, it's obviously > useful.) Yes, there is some confusion: they are the same thing, C-c C-v is basically a shortcut for C-c C-c View RET RET. I'm honestly lost. Could you please explain what's the workflow you'd like to use? I thought it's something like this: 1) edit the source in AUCTeX 2) compile it with C-c C-c 3) open the output document in Okular with C-c C-v 4) switch back to Emacs with the window manager (usually ALT + TAB, I guess) 5) edit again 6 compile again with C-c C-c 7) switch to Okular with the window manager. The document will auto-reload 8) reiterate from point 4 If this is your workflow, forward search can't be used --- C-c C-v is run only once at point 3 --- unless you close Okular all the time. Perhaps I'm wrong, so please explain it more clearly. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#29525: Please don't default to "--unique" mode for Okular
2017-12-03 10:26 GMT+01:00 Reuben Thomas : >> If you are working with many documents at the same time (say 3-4 or >> even more) switching between Emacs and the wanted document can be >> really annoying, using C-c C-v brings to focus the right instance of >> the viewer. This is what Evince does and is much more convenient. > > > I agree, but this is a problem to solve with the window manager, not the > application behaviour. I don't see how it's a problem of the windows manager. I happen to have several programs open at the same time and often switch between them. For example, I'm using the terminal, than switch to Emacs and want to see the output document. The next window that can be reached by ALT + TAB is the terminal, not Okular, how could the window manager guess I want to switch directly to the document viewer? I missed to stress one important point of C-c C-v: when forward search is enabled --- and I guess most of us has it on --- C-c C-v moves the viewer to the corresponding point, this isn't something that can be achieved by simply switching to the viewer with ALT + TAB. Thus, removing the --unique option now would make extremely annoying using forward search with Okular. As I already stated, I agree that currently working with multiple documents can be inconvenient, but breaking usage of forward search doesn't look a solution to me. Fixing the behavior of Okular seems a better approach. After that, the --unique option is surely not needed anymore. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#29525: Please don't default to "--unique" mode for Okular
2017-12-02 19:52 GMT+01:00 Reuben Thomas : > Thanks very much to both of you for your feedback. > > On 1 December 2017 at 21:49, Arash Esbati wrote: >> >> >> it is also the default for Yap, dviout, SumatraPDF. And this is the >> problem with defaults: Never 100% satisfied customers. > > > The problem in this case is not the default per se (though it is hard to > work out how to configure it: the customize interface for this setting is > overcomplicated), it is that the default is different for different > previewers. The default should (as far as possible) be the same, so that > changing viewers does not change the behaviour. > > Mosè said: "Without this option you'll need to close Okular to view again > (C-c C-v) the document without spawing several instances of the viewer for > the same document." > > This is not exactly true: once Okular (or Evince) has been spawned, there is > no need to run the View command again: both viewers auto-reload. You're saying that it isn't necessary, this doesn't make my previous statement false --- I mentioned C-c C-v for a reason. Switching to the viewer with C-c C-v is what I do, rather than using the window manager to get to the viewer: I have always several programs open at the same time, Emacs' and Okular's windows are rarely the closest ones. Also, C-c C-a opens the viewer with TeX-view at the end of compilation, but this is optional. The more I think about this, the more I'm convinced that the issue you raised is sensible but the best solution would be to fix first upstream in Okular. It'd be a good improvement. After that, I'll be more than happy to remove the --unique option. If you are working with many documents at the same time (say 3-4 or even more) switching between Emacs and the wanted document can be really annoying, using C-c C-v brings to focus the right instance of the viewer. This is what Evince does and is much more convenient. > For the Customize interface, I'm not sure what to suggest. The current > interface is far too complicated, but if it were made simpler (e.g. to have > a "single instance" toggle) then it would not be so general. This is an interesting suggestion but probably not so easy to adopt. > Arash, you mention editing .emacs; this is a shame. Please, there is no need to put shame on anyone. > It's not the 1990s any > more: I don't even have a .emacs file, I have .emacs.d/init.el I honestly don't get what you mean here. > but more to > the point, the default should be to say "customize foo to bar". To advise > editing .emacs is either a) confusing, b) an admission that Customization > isn't manageable, or c) both. Well, he did suggest you to customize `TeX-view-program-list', *and* provided you, as a possibility, with two lines of code to add to your init file to accomplish the same task. It's up to you to decide what's best for you. I really don't see what's the problem here. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#29525: Please don't default to "--unique" mode for Okular
Hi Reuben, 2017-11-30 22:57 GMT+01:00 Reuben Thomas : > I noticed that Emacs seemed only ever to start one instance of Okular, which > makes it impossible to view multiple files side-by-side. I tracked this down > to its use of --unique. While there may well be users who prefer this style, Without this option you'll need to close Okular to view again (C-c C-v) the document without spawing several instances of the viewer for the same document. > I suggest that it shouldn't be the default in AUCTeX, because it's not the > default for other viewers. In this regard Evince is smarter than Okular, doesn't create a new instance for the same document if already open. I'm not saying the default shouldn't be changed, but I personally like it because I more often work on a single document rather than multiple at once. I'd like to hear comments from other users on this. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#29398: company-minimum-prefix-length
Hi Tassilo, 2017-11-23 9:04 GMT+01:00 Tassilo Horn : > Hi all, > > I've removed the code. The argument that many users also use the > dabbrev company backend in combination with the native completion of the > mode made sense. In that case, you might have thousands of completions > with a too short prefix length. Great! Thanks for taking care of this. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25002: Fail to preview latex in macOS emacs
Hi Michael, adding to what David said, we'll hopefully release a new stable version of AUCTeX, which will include the fix, by next week. Bye, Mosè 2017-11-23 9:10 GMT+01:00 Michael Heerdegen : > David Kastrup writes: > >> That's a different bug (actually several different bugs). Ghostscript >> has a history of changing its security-related behavior around, and >> every time preview-latex stops working until another patch is committed >> to AUCTeX. Ghostscript 9.22 finally removed a security related feature >> (the .runandhide operator) without working secure replacement. A fix >> has already been committed to upstream AUCTeX: this was comparatively >> straightforward to do since preview-latex had in a previous iteration >> already removed security-relevant reliance on this operator in order to >> stop this game, but it had still relied on its use elsewhere. > > Ok, it was just a shot in the dark. Thanks for explaining. > > > Michael. > > > > ___ > bug-auctex mailing list > bug-auctex@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-auctex > ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#29401: 11.90.2.2017-07-25; Folding displays errors on valid LaTeX
Dear Koen,
2017-11-22 17:55 GMT+01:00 Koen van Greevenbroek
:
> Hi!
>
> Some valid LaTeX is parsed incorrectly by AUCTeX folding functions
> (i.e. 'TeX-fold-region'), and an annoying error is displayed. Here is
> an
> example:
>
> ===
> \documentclass{beamer}
> \begin{document}
> \begin{frame}
> \begin{itemize}
> \item \textbf<1>{One}
> \item \textbf<1>{Two}
> \end{itemize}
> \end{frame}
> \end{document}
> ===
>
> When folded, this code is displayed as follows:
>
> ===
> \documentclass{beamer}
> \begin{document}
> \begin{frame}
> \begin{itemize}
> * [Error: No content found]<1>{One}
> * [Error: No content found]<2>{Two}
> \end{itemize}
> \end{frame}
> \end{document}
> ===
>
> Another example, which doesn't involve beamer, is the following code:
>
> ===
> \usepackage{titlesec}
> \titleformat{\section}{\bfseries}{\thesection}{10pt}{}[\normalfont]
> ===
>
> which displays as:
>
> ===
> \usepackage{titlesec}
> \titleformat{[Error: No content
> found]}{\bfseries}{\thesection}{10pt}{}[\normalfont]
> ===
>
> Maybe it would be an idea to just not fold things like this where no
> content it found, instead of displaying an error?
Thanks for the detailed report. I tried at least to track down the
culprit for the beamer case, I think a general solution would be to
teach `TeX-find-macro-boundaries' and related functions about <...>
specifications. Unfortunately, I don't have right now the time to fix
it, but this should be a starting point for anyone willing to tackle
this issue. Regarding the second case, I don't think there is an easy
fix for it.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#29398: company-minimum-prefix-length
Hi Fred, 2017-11-22 10:11 GMT+01:00 Frederik Beaujean : > Dear auctex developers, > > I'm using auctex with the company completion system. The problem is that > > company-minimum-prefix-length > > is ignored in tex files. This is annoying when typesetting math with the > usual single-character symbols like i or n because I have to press C-g > multiple times to turn of the completion overlay. > > I had initially posted this issue on github with spacemacs and > company-auctex, it affects several people as well > > https://github.com/syl20bnr/spacemacs/issues/9388 > > https://github.com/alexeyr/company-auctex/issues/18 > > The root of the problems seems this code in auctex/tex.el in v11.91 > > ;; By default, company completions kick in after a prefix of 3 chars has > ;; been typed. Since we don't have too many completions, that's too > ;; much. > (set (make-local-variable 'company-minimum-prefix-length) 1))) > > I don't understand the explanation given for creating this local variable. I > request that it be removed or done in such a way that it doesn't override > global user settings. You can override this setting with (add-hook 'TeX-mode-hook '(lambda () (setq company-minimum-prefix-length 3))) However, I see that you'd like to avoid setting again the option. Tassilo, could you please give a look at this? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#28953: 11.91.0; wrong alert about inexistent LaTeX errors
2017-10-24 9:25 GMT+02:00 jfbu :
> What about spaces? I know there isn't
> a single file with spaces in its path on my TeX installation,
> and I personally will never ever attempt to use such in my
> TEXMFHOME or in the document repertory or sub-repertories.
TeX and AUCTeX don't have problems with spaces in file names. I also
avoid spaces in file names, but asking people to completely stop using
spaces in order to make AUCTeX work doesn't look good.
> People doing
>
> \section{foo}\label{sec:1: (authorA)}
>
> See \ref{sec:1: (authorA)}
>
> will similarly get bitten by this problem.
Are there really people mixing numeric style and literal style in
labels? :-) Using anything beside [a-zA-Z0-9-:] in LaTeX labels is
usually a bad idea, just because there are packages playing with
catcodes. For example, underscores are legal in labels, but there are
cases where you can get into troubles if you use them, see for example
https://tex.stackexchange.com/q/121416/31416 or
https://tex.stackexchange.com/a/18312/31416.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#28953: 11.91.0; wrong alert about inexistent LaTeX errors
2017-10-23 18:35 GMT+02:00 jfbu :
>
> Le 23 oct. 2017 à 17:09, Mosè Giordano a écrit :
>
>> 2017-10-23 14:47 GMT+02:00 jfbu :
>>> In real life example the ``:1: `` pattern appeared farther away on the line
>>> inside a sentence. To a human, it is obvious it is not a LaTeX error
>>> message. I am confident the logic for recognizing such error messages
>>> is improvable. I plan to look at it when I get time to make
>>> concrete proposal.
>>
>> The relevant regexp is at line 1507 of tex-buf.el:
>> https://git.savannah.gnu.org/gitweb/?p=auctex.git;a=blob;f=tex-buf.el;h=f458651c2cffc110ef4af4541c6b08af976907fb;hb=HEAD#l1507
>> Perhaps ".*" is too greedy, anyway that regexp should match anything
>> that is a legal path. I don't expect it to be supereasy to find a
>> regexp matching a path but not a whole sentence ;-)
>
>
> Indeed. But the regexp is really minimal, is there some documentation
> about the underlying difficulties?
I don't think there is such documentation, but I'd be happy to be proven wrong.
As far as I know, using exclamation mark to start an error message is
just a widespread convention, there is nothing fundamental in it. For
the file-line-error style, the first part should match a file path. I
don't know if it **has** to start with "./" (or "/"), or it may change
depending on the TeX version (and for sure it depends on the platform
used). The file may end with an extension (AUCTeX doesn't really like
files without any extension), but TeX doesn't require it at all.
> Reporting that the LaTeX run had errors, and giving an Error overview
> could perhaps be split.
>
> For example if I try this
>
> \documentclass{article}
> \begin{document}
> Hi
> \typeout{./I/am/not/a/file:4: and this is not an error}
> \typeout{}
> \ERROR
> \typeout{}
> \typeout{! I am not an error.}
>
> Did it go OK?
> \end{document}
>
> with Latexmk, it will only say
>
> Collected error summary (may duplicate other messages):
> latex: Command for 'latex' gave return code 1
> Refer to 'temp2.log' for details
>
> Without the \ERROR, it reports no problem. Now, indeed
> Latexmk does not report a detailed error summary like AUCTeX
> (it does report undefined references etc...)
>
> For example a \PackageError{foo}{zaza}{tata} will also
> cause the latex run to exit with return code 1 on my mac os,
> hence the return code detects it independently of log contents.
>
> Could AUCTeX check the return code on platforms allowing it?
This is interesting, but should be implemented in a reliable way.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#28953: 11.91.0; wrong alert about inexistent LaTeX errors
2017-10-23 14:47 GMT+02:00 jfbu : > In real life example the ``:1: `` pattern appeared farther away on the line > inside a sentence. To a human, it is obvious it is not a LaTeX error > message. I am confident the logic for recognizing such error messages > is improvable. I plan to look at it when I get time to make > concrete proposal. The relevant regexp is at line 1507 of tex-buf.el: https://git.savannah.gnu.org/gitweb/?p=auctex.git;a=blob;f=tex-buf.el;h=f458651c2cffc110ef4af4541c6b08af976907fb;hb=HEAD#l1507 Perhaps ".*" is too greedy, anyway that regexp should match anything that is a legal path. I don't expect it to be supereasy to find a regexp matching a path but not a whole sentence ;-) Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#28953: 11.91.0; wrong alert about inexistent LaTeX errors
Hi Jean-François,
2017-10-23 11:11 GMT+02:00 jfbu :
> Hi, here is minimal example:
>
> \documentclass{article}
> \begin{document}
> \typeout{Hello:1: }
> \end{document}
>
> This triggers AUCTeX log parser to report wrongly
> that there were compilation errors.
>
> The two colons and the space conspire to this result.
>
> It happened in real life example.
I think you're asking too much :-) I don't see any meaningful way to
distinguish between a real error and a message you write to the log
that is exactly equal to the file-line-error style. The same happens
with \typeout{! hello world}.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#28905: 11.90.2.2017-07-25; TeX-documentation-texdoc blocks
Hi Keita, 2017-10-22 15:13 GMT+02:00 Ikumi Keita : > Hi Fran and Mosè, > >>>>>> Mosè Giordano writes: >> Hi Fran, >> 2017-10-19 23:38 GMT+02:00 Fran Burstall (Gmail) : >>> Greetings! >>> >>> I do >>> >>> M-x TeX-documentation-texdoc >>> >>> and supply the argument amsmath when prompted. An evince >>> window fires with the documentation but emacs is blocked >>> until I exit evince. >>> >>> If I try the same thing with tex-doc, evince fires but emacs >>> remains usable. >>> >>> Experiment suggests that the former uses >>> shell-command-to-string and this blocks while the latter > >> That's true, but I can't reproduce your issue. > > Fran's problem reproduces on my machine. The output of > TeX-sumit-bug-report is at the tail of this message. > >> What happens if you run > >> texdoc amsmath > >> in your terminal? For me the viewer is opened in the background, so >> the shell is free and the prompt readily appears, without waiting for >> the viewer to be closed. Isn't this the case for you? > > My result is the same as Fran's, too. On my kterm (xterm variant > capable of dealing with Japanese texts), the viewer is opened in the > background, the shell is free and the prompt readily appears, without > waiting for the viewer to be closed. > > It doesn't help to change the part > (concat "texdoc --view " pkg) > in `TeX-documentation-texdoc' to > (concat "exec texdoc --view " pkg " &") > for my case. It seems that emacs grabs something of the subprocess of > the shell and does not release it until all(?) of subprocess terminate. Thanks for sharing your experience. The problem with texdoc program is that it doesn't use return status in a meaningful way. There is no way to know if it was able to find a documentation for the requested package besides reading the output. Try this: $ texdoc foobar Sorry, no documentation found for foobar. If you are unsure about the name, try searching CTAN's TeX catalogue at http://ctan.org/search.html#byDescription. $ echo $? 0 Fran, as a workaround you can bind `TeX-doc' to C-c ? with (with-eval-after-load "tex" (define-key TeX-mode-map (kbd "C-c ?") 'TeX-doc)) even if I'd like to find a solution to keep `TeX-documentation-texdoc' working. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#28905: 11.90.2.2017-07-25; TeX-documentation-texdoc blocks
Dear Fran, please, when you reply to mailing lists use the "Reply all" button, so that the message will be delivered to all readers, not just me, and recorded in the bug tracker. 2017-10-20 1:10 GMT+02:00 Fran Burstall (Gmail) : > Hi Mosè, > > Yes, I get the same behaviour as you in the terminal: the prompt reappears > almost at once and evince fires. > > However, in the scratch buffer of my emacs, evaluating > > (shell-command-to-string "texdoc --view amsmath") > > blocks emacs (I even get an OS rotating busy timer for a pointer until the > evince window is closed) while evaluating > > (call-process "texdoc" nil 0 nil "--view" "amsmath") > > gives me a non-blocked emacs while the evince window is open. > > Any ideas? Not really. Anyone else has a clue of what may be going on here? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#28905: 11.90.2.2017-07-25; TeX-documentation-texdoc blocks
Hi Fran, 2017-10-19 23:38 GMT+02:00 Fran Burstall (Gmail) : > Greetings! > > I do > > M-x TeX-documentation-texdoc > > and supply the argument amsmath when prompted. An evince > window fires with the documentation but emacs is blocked > until I exit evince. > > If I try the same thing with tex-doc, evince fires but emacs > remains usable. > > Experiment suggests that the former uses > shell-command-to-string and this blocks while the latter That's true, but I can't reproduce your issue. What happens if you run texdoc amsmath in your terminal? For me the viewer is opened in the background, so the shell is free and the prompt readily appears, without waiting for the viewer to be closed. Isn't this the case for you? > uses call-process to fire texdoc and this does not block > (or, at least, exits once texdoc has handed off to evince). > > Thanks for the wonderful package! You're welcome! Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#28456: 11.90.2.2017-07-25; \\input parsing
Hi Pierre,
2017-09-14 7:55 GMT+02:00 Pierre Lorenzon :
> As if second \input
> \input{../../Exercices/Ensembles/Applications-Proprietes}
>
> were not parsed when first one
>
> \input{Introduction}
>
> is. In fact looking carefully at regexp used to match \\input
> which is part of the LaTeX-auto-regexp-list variable, it
> clearly appears that an path like \input{../../something} will
> not be parsed.
I can reproduce the error and confirm your analysis.
> Question is why? When LaTex allows inputs with so complexe
> paths, why are they not parse by auctex?
It's hard to answer the question: that regexp has been there for more
than 20 years now ;-)
I don't have the time to do it now (I also have a flaky Internet
connection in this period), but if someone wants to tackle this issue,
I fixed something similar for \addbibresource a few months ago:
* b2f69e18 (2017-03-31) Fix detection of bibliography files with
dots in path
Please, also add a test. Maybe this could be an occasion to review
similar regexps (for \include, \bibliography, etc), or maybe have a
common variable for all this cases.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#27602: 11.89; non-character input; Aquamacs blocked
Hi Albert, 2017-07-06 22:19 GMT+02:00 Albert Fisher : > This bug has occured before periodically. When I am editing my file, it > blocks and I need to type "p" for permission for every keystroke, which of > course is extremely annoying and also leads to errors. I then change from > "Master File" to "Buffer" , and sometimes it works again. If not, I kill > Aquamacs and Skim and usually it works properly upon restart. > If not, I restart the laptop and pray. Just now, I let the computer fall > asleep and was greeted by this error when I returned, and killing Aquamacs > and Skim didn't help so I guess I'll restart. Sorry, I don't understand what happens here, maybe because I don't use Aquamacs but plain Emacs. While editing a *TeX file Aquamacs freezes without apparent reason? Why do you have to press "p" for permissions? What you mean by «I then change from "Master File" to "Buffer"»? What's that you change? I can't think of any known issue in AUCTeX that can lead to freezing Emacs. It would be great if you could find a common operation that you perform whenever Aquamacs freezes. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#27213: 11.90.2; Display geometry unavailable: Wrong type argument: number-or-marker-p, nil
Hi Jorge,
2017-06-03 17:33 GMT+02:00 Jorge Moreira :
> Display geometry unavailable: Wrong type argument: number-or-marker-p, nil
>
> Emacs : GNU Emacs 25.2.1 (x86_64-apple-darwin16.4.0)
> of 2017-04-24
> Package: 11.90.2
>
> Run buffer contents:
>
> Running `LaTeX' on `thesis' with ``pdflatex -file-line-error
> -interaction=nonstopmode "\input" thesis.tex''
> This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/MacPorts
> 2016_5) (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> LaTeX2e <2016/03/31>
> Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
> (./thesis.tex (/opt/local/share/texmf-texlive/tex/latex/base/article.cls
> Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
> (/opt/local/share/texmf-texlive/tex/latex/base/size10.clo)) (./thesis.aux)
> [1{/opt/local/var/db/texmf/fonts/map/pdftex/updmap/pdftex.map}]
> (./thesis.aux)
> )
> Output written on thesis.pdf (1 page, 22941 bytes).
> Transcript written on thesis.log.
>
> TeX Output finished at Sat Jun 3 11:29:42
Can you please provide some more information? For example, a recipe
to reproduce the issue.
Thanks,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#27139: Inline math in "\(\)" pairs won't highlight in captions
Hi!
2017-05-30 2:28 GMT+02:00 Hong Xu :
> The following minimal example
>
> \documentclass{article}
>
> \begin{document}
> \begin{figure}
> \centering
> \caption{Math \(x=y\) and $x=y$.}
> \end{figure}
> \end{document}
>
> $x=y$ is highlighted but \(x=y\) is not. Perhaps both should be highlighted?
Yes, I agree this is an inconsistent behavior, but you already
reported the issue one month ago:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26630 ;-)
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#26694: preview-at-point fails on very long lines with "End of buffer"
2017-05-29 16:33 GMT+02:00 Ikumi Keita : > Gosh, these viewers use emacslient on reverse search, which ends up with > opening _region_.tex buffer instead of the original document's buffer > when using region file. Then it's not so useful to arrange the > expanders to work with region file in forward search... Exactly. In the case of Evince (and Atril) and pdf-tools, AUCTeX can talk with the viewer and tell it that to go back to the original document. This isn't possible in other cases, where the viewers only read the SyncTeX file, which points to _region_.tex. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#26694: preview-at-point fails on very long lines with "End of buffer"
Hi Keita,
2017-05-28 15:12 GMT+02:00 Ikumi Keita :
> I looked into this problem and would like to share my thoughts about
> this.
Thanks! As I said, mine was more a workaround rather than a real fix,
I'm happy someone else is addressing the issue :-)
> (1) Some problems of the essentially same origin still remain.
>(a) Open Frank's sample file and enable TeX-source-correlate-mode.
>(b) Put the region over "$x$".
>(c) Type C-c C-p C-r. "End of buffer" error again. C-c C-r gives
>the same error, too.
>
> Here is the relavant codes Mosè modified in tex-buf.el:
> (when TeX-source-correlate-mode
> (let ((line-col (with-current-buffer orig-buffer
>(cons (TeX-line-number-at-pos)
> (current-column)
>(goto-char (point-min))
>(forward-line (1- (abs (- header-offset (car line-col)
>(forward-char (cdr line-col
> It is this `forward-char' that raises the error. The number
> returned by `(current-column)' is not correct when, in original
> buffer, the region starts in the middle of a line and the point is
> on the first line of the region. If a relatively small region has
> no newline in it and is put on the rightward enough of a very long
> line, the returned value is too large for `forward-char'.
>
> (2) We can find a function `TeX-region-update-point', which does a
> similar job but without adjustment of the column. I suppose we can
> unify them.
>
> Considering that, in addition to (1) and (2), update of the position of
> the point in _region_.tex is only necessary when we invoke viewer, call
> to `TeX-region-update-point' can be summarized in `TeX-command' with
> test of `(string= name "View")'.
>
> I made a tentative patch along these idea and attached it to this
> message. I stopped using `current-column' and use difference betewwn
> point and max{beginning of line, beginning of region}.
I like your approach! In addition, this doesn't need changing the
arguments of `TeX-region-create', that's what I wanted to avoid.
> (3) It seems that the feature of forward and inverse search for region
> file is not mature yet. If I understand correctly, it works only
> with evince, atril and pdf-tools as viewer, right?
Evince and Atril yes (see release notes for AUCTeX 11.89), I don't
know about pdf-tools but it's possible.
> The other
> viewers in `TeX-view-program-list-builtin' receive the file name and
> line number with "%b" and "%n" expanders, but these are not expanded
> to suitable value when using region file.
> Maybe we should add other expanders which work even with region
> file.
Other expanders? Why not adapting the existing ones? Anyway, I'm not
sure that inverse search would work with other viewers.
> (4) Using `current-column' might not be suitable even when we use evince
> or atril. The function `TeX-evince-sync-view-1' passes required
> parameters to the viewers like this:
>(list :struct :int32 (TeX-line-number-at-pos)
> :int32 (1+ (current-column)))
> Most of CJK letters count as occuping 2 columns, so the column
> number is not equal to the number of the characters counting from
> the beginning of a line. (I don't know what is the correct
> "column" parameters for evince and atril (number of letters?
> bytes in UTF8? or other?), so don't know how we should change this
> part.)
I don't know, sorry.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25322: preview-latex coding system problem with Japanese LaTeX
2017-05-26 19:11 GMT+02:00 Ikumi Keita : > Hi Mosè, thanks for your response! > >>>>>> Mosè Giordano writes: >> Indeed I have a problem: all non skipped tests in >> japanese/preview-latex.el fail for me. Attached you can find the log, >> if it can help you. > > It seems that the latest commit is not yet installed on your box. I > encountered similar fails with AUCTeX before the update. My tests only > pass with the updated codes. The repo was up-to-date, but I had to make distclean before recompiling AUCTeX (before I run only make clean, which wasn't sufficient). Now the tests pass. Thanks and sorry for the noise! Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25322: preview-latex coding system problem with Japanese LaTeX
Hi!
2017-05-26 15:47 GMT+02:00 Ikumi Keita :
> I wrote a suite of ERT files and commited them with the patches, since I
> heard no objections during the span. I also commited the patch in my
> previous message to make preview-latex to work with xemacs on w32
> system.
>
> Since it was too difficult for me to write a full automated test which
> can complete entirely in batch mode because the functionality of
> preview-latex depends how images scattered on the buffer "look" like to
> human eyes, some of the tests are marked to be skipped in batch mode.
> Such tests requires manual execution instead.
I know that tests aren't always easy to write, especially for stuff
that requires interaction. I don't ask tests at any cost, but when
it's possible to write them, they're definitely useful to prevent
future failures ;-)
> If someone finds difficulties with this commit, feel free to ask me.
Indeed I have a problem: all non skipped tests in
japanese/preview-latex.el fail for me. Attached you can find the log,
if it can help you.
Bye,
Mosè
Loading 00debian-vars...
Loading /etc/emacs/site-start.d/50autoconf.el (source)...
Loading /etc/emacs/site-start.d/50cmake-data.el (source)...
Loading /etc/emacs/site-start.d/50dictionaries-common.el (source)...
Loading debian-ispell...
Loading /var/cache/dictionaries-common/emacsen-ispell-default.el (source)...
Loading /var/cache/dictionaries-common/emacsen-ispell-dicts.el (source)...
Loading /etc/emacs/site-start.d/50emacs-goodies-el.el (source)...
Loading /etc/emacs/site-start.d/50festival.el (source)...
Loading /etc/emacs/site-start.d/50python-docutils.el (source)...
Running 8 tests (2017-05-26 17:29:15+0200)
Test japanese-preview-convert-^^ab backtrace:
(let ((fn-65 (function string=)) (args-66 (list (preview--convert-^^
(let (case-fold-search) (let ((fn-65 (function string=)) (args-66 (l
(lambda nil (let (case-fold-search) (let ((fn-65 (function string=))
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test japanese-preview-convert-^^ab "`pre
ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test j
ert-run-tests(t #[385 "\306\307\"\203G \211\211G\310U\203 \211@\20
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
command-line-1(("-L" ".." "-l" "ert" "-l" "japanese/preview-latex.el
command-line()
normal-top-level()
Test japanese-preview-convert-^^ab condition:
(void-function preview--convert-^^ab)
FAILED 1/8 japanese-preview-convert-^^ab
Test japanese-preview-decode-^^ab backtrace:
(let ((fn-45 (function string=)) (args-46 (list (preview--decode-^^a
(let (case-fold-search) (let ((fn-45 (function string=)) (args-46 (l
(lambda nil (let (case-fold-search) (let ((fn-45 (function string=))
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test japanese-preview-decode-^^ab "`prev
ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test j
ert-run-tests(t #[385 "\306\307\"\203G \211\211G\310U\203 \211@\20
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
command-line-1(("-L" ".." "-l" "ert" "-l" "japanese/preview-latex.el
command-line()
normal-top-level()
Test japanese-preview-decode-^^ab condition:
(void-function preview--decode-^^ab)
FAILED 2/8 japanese-preview-decode-^^ab
skipped 3/8 japanese-preview-different-coding-system
Test japanese-preview-error-quote-shift-jis backtrace:
(setq value-42 (apply fn-40 args-41))
(unwind-protect (setq value-42 (apply fn-40 args-41)) (setq form-des
(if (unwind-protect (setq value-42 (apply fn-40 args-41)) (setq form
(let (form-description-44) (if (unwind-protect (setq value-42 (apply
(let ((value-42 (quote ert-form-evaluation-aborted-43))) (let (form-
(let ((fn-40 (function string-match)) (args-41 (list (preview-error-
(while --dolist-tail-- (setq str (car --dolist-tail--)) (let ((fn-40
(let ((--dolist-tail-- (quote ("表(1)" "予{a}" "能|" "{あ} %能" "アース" "型"
(let (case-fold-search (buffer-file-coding-system (quote shift_jis))
(lambda nil (let (case-fold-search (buffer-file-coding-system (quote
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test japanese-preview-error-quote-shift-
ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test j
ert-run-tests(t #[385 "\306\307\"\203G \211\211G\310U\203 \211@\20
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
command-line-1(("-L" ".." "-l" "ert" "-l" "japanese/preview-latex.el
command-line()
normal-top-level()
Test japanese-preview-error-quote-shift-jis condition:
(invalid-regexp "Unmatched ( or \\(")
FAILED 4/8 japanese-preview-error-quote-shift-jis
skipped 5/8 japanese-preview-preserve-kanji-option
Applying style hooks...
Applying style hooks... done
Applying style hooks...
Applying style hooks... done
Type `C-c C-l' to display results of compilation.
No files t
bug#25322: Acknowledgement ([AUCTeX-devel] preview-latex coding system problem with Japanese LaTeX)
Hi Keita, 2017-05-18 15:32 GMT+02:00 Ikumi Keita : > Hi all, > > I worked on to resolve the remaining problems with respect to the > incompatibility between preview-latex and Japanese LaTeX, and think that > I managed to sort out them. Please take a look at the attached patch. > > My basic plan, in addtion to the part described before in > http://lists.gnu.org/archive/html/auctex-devel/2016-09/msg00101.html > , is > (1) Implement in tex-buf.el a function to adjust the process coding > system for normal tex documents as well as Japanese tex documents > and make it the new default value for > `TeX-after-start-process-function', which was previously used only > for Japanese TeX by tex-jp.el. With this change, all tex processes > invoked within AUCTeX are given suitable coding systems. > (2) Make preview-latex to examine the coding system set in (1), and > use it to decode later if it decides not to decode during receiving > outputs and to store them as byte sequence in order to work around > xemacs bug. To achieve this, the patch changes the meaning of the > variable `preview-coding-system'. Its value used to be the "new" > coding system, which is potentially `raw-text' preserving the byte > sequence, but it's now the "original" coding system assigned to the > process, which decodes the outputs properly. > > Any comments and suggestions are greatly welcome. I only read the patch, didn't actually try it, but I'm confident you did it ;-) I didn't see anything clearly wrong. I have only a request: do you think it's possible to add a test for this fix? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#26694: preview-at-point fails on very long lines with "End of buffer"
Hi Frank, 2017-04-28 15:26 GMT+02:00 Frank Fischer : > However, I would say the the column offset is just wrong. Either > subtract the length of the preceding text (in the original buffer) from > the column number or copy the preceding text to the temp buffer as well. I think you're right, a good solution would be to add one more argument to `TeX-region-create' with the adjusted line-col information. However, in order to avoid changing the signature of the function I decided to apply a work around: the point is moved only when `TeX-source-correlate-mode' is non nil (because point is moved only to make forward/inverse search work) and this variable is let-bound to nil when running the preview (forward/inverse search is not needed here). I dropped a few comments about this work-around in the code, in case someone want to improve the fix, maybe as suggested above. In any case, I'm closing this ticket as the issue should be fixed. Thanks for the good bug report Frank! Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#26694: preview-at-point fails on very long lines with "End of buffer"
Hi Frank, 2017-04-28 15:26 GMT+02:00 Frank Fischer : > Hi, > > consider the following example file https://pastebin.com/73W7EbCa > > This file has a single very long line with one math item at the end. Do > the following: > > 1. generate the preview with C-c C-p C-p > 2. move point to the "x" in the math block, change it to "y" and leave > point within the math block > 3. execute C-c C-p C-p again > > One should get the message "End of buffer" without the preview being > regenerated. > > AFAICT the reason is that in this case only the snippet $x$ without the > text preceding the snippet in the line is copied to the temporary file > for generating the preview. However line 2103 in tex-buf.el (that is the > line with "(forward-char (cdr line-col))") tries to move point to the > *original* column of the snippet. This number is so large that > "(forward-char ...)" will actually reach the end of the buffer and the > error occurs. > > However, I would say the the column offset is just wrong. Either > subtract the length of the preceding text (in the original buffer) from > the column number or copy the preceding text to the temp buffer as well. > > I hope my description is clear, if not, please ask ;) Thanks for the detailed bug report, I can reproduce it. However, right now I don't have the time to dig into it, but I found that the issue should be in `TeX-region-create' and can be reproduced with point on the "y" with --8<---cut here---start->8--- (preview-region (preview-next-border t) (preview-next-border nil)) --8<---cut here---end--->8--- If someone else wants to look into it, please go ahead. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#26125: ispell fails to detect certain typos
Hi Leon, 2017-03-16 13:29 GMT+01:00 Leon Meier : > Used packages: > - auctex 11.90.0, > - emacs 24.3.1 (24.3-22.1 on OpenSuse), > - ispell 3.3.02 (3.3.02-113.1 on OpenSuse), > - ispell-american (american.aff v 1.23, 3.3.02-113.1 on OpenSuse) > > Bug description: > > Create the file q.tex with the following contents (without the square > brackets): > [ > \(\sigma\) contradition > > %%% Local Variables: > %%% ispell-local-dictionary: "american" > %%% End: > ] > > Then, open q.tex with emacs when auctex is loaded. Issue > M-x ispell-buffer > > Observe that the typo in the word "contradition" remains unnoticed. For the record, I cannot reproduce this on my machine (Debian testing). I have "aspell" as `ispell-program-name', not sure if this is relevant. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#26085: Formatting of AUCTeX Reference Card
Hi Tristan, 2017-03-13 16:31 GMT+01:00 Tristan Miller : > Dear all, > > Is there any chance the AUCTeX Reference Card could be reformatted so > that it is suitable for folding? The three columns suggest that the > card is meant to be printed in duplex and folded accordion-style, but > this turns out not to work because both sides of the page have a wide > right margin. If all three columns were the same width (as I suspect > they already are), and uniformly distributed across the page, then the > accordion fold would work nicely. I suspect that the refcard is tailored to letter paper size. It has almost the same code as the Emacs refcard, which looks fine on that paper format[1], but if compiled for A4 is as unbalanced as the AUCTeX refcard. I don't think I have the ability to fix this, for sure in this period I don't have the time to look deeper, but patches to make the refcard work on A4 paper are welcome. Bye, Mosè Note: [1] https://www.gnu.org/software/emacs/refcards/pdf/refcard.pdf ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug-auctex@gnu.org
Hi Arash, have you been writing many tables lately? ;-) 2017-03-08 20:43 GMT+01:00 Arash Esbati : > My suggest to guard (- (current-column) 1) with a (wholenump ...) and > return (+ 2 beg-col) as fallback if the test is not true: Yeah, a fallback option in case we get non-sense result is always useful. Alas, `wholenump' is not available in XEmacs. Remember also the test! Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug-auctex@gnu.org
Hi Arash, 2017-03-07 14:24 GMT+01:00 Arash Esbati : > AUCTeX doesn't see the control symbol \&, it just takes the ampersand as > a column separator. This issue is caused in the last part of the > function `LaTeX-indent-tabular': Good catch. I like the solution proposed by Keita, with or without `TeX-escaped-p' (but I slightly prefer using these generic functions). If you're going to install the fix, please add a test as well. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25674: Support for subfiles in `reftex-TeX-master-file'
Hi Arash,
2017-02-10 9:48 GMT+01:00 Arash Esbati :
> Hi all,
>
> the function `reftex-TeX-master-file' in `reftex.el' has support for
> subfiles package, but I think the regexp there does not match all
> cases. Please consider a main file "subfile-main.tex" and a sub-file
> "subfile-sub1.tex" like these:
>
> --8<---cut here---start->8---
> \documentclass{article}
> \usepackage{subfiles}
> \begin{document}
>
> \section{Section 1}
> \label{sec:section-1}
>
> \subfile{subfile-sub1.tex}
> \end{document}
>
> %%% Local Variables:
> %%% mode: latex
> %%% TeX-master: t
> %%% End:
> --8<---cut here---end--->8---
>
> --8<---cut here---start->8---
> \documentclass[subfile-main.tex]{subfiles}
> \begin{document}
>
> \section{Subsection 1}
> \label{sec:subsection-1}
>
> \end{document}
>
> %%% Local Variables:
> %%% mode: latex
> %%% TeX-master: t
> %%% End:
> --8<---cut here---end--->8---
>
> `reftex-TeX-master-file' fails to parse the first line and find out the
> main file due to first part of it:
>
> --8<---cut here---start->8---
> (defun reftex-TeX-master-file ()
> ;; Return the name of the master file associated with the current buffer.
> ;; When AUCTeX is loaded, we will use it's more sophisticated method.
> ;; We also support the default TeX and LaTeX modes by checking for a
> ;; variable tex-main-file.
> (let
> ((master
> (cond
> ;; Test if we're in a subfile using the subfiles document
> ;; class, e.g., \documentclass[main.tex]{subfiles}. It's
> ;; argument is the main file, however it's not really the
> ;; master file in `TeX-master-file' or `tex-main-file's
> ;; sense. It should be used for references but not for
> ;; compilation, thus subfiles use a setting of
> ;; `TeX-master'/`tex-main-file' being themselves.
> ((save-excursion
> (goto-char (point-min))
> (re-search-forward
>
> "^[[:space:]]*documentclass\\[\\([[:word:].]+\\)\\]{subfiles}"
> nil t))
> (match-string-no-properties 1))
> --8<---cut here---end--->8---
>
> The regexp looks for [:word:] character class and ignores anything
> else. Using `-', `_' or digits in main file name will not work.
Agreed.
> I
> think the regexp can be reduced to
>
> --8<---cut here---start->8---
> (re-search-forward
> "^[[:space:]]*documentclass\\[\\([^]]+\\)\\]{subfiles}"
> nil t))
> --8<---cut here---end--->8---
>
> as `reftex-TeX-master-file' checks if .tex extension is given or not.
> With this change, one can use `C-c )' over all files in a project and
> `C-c C-c' compiles a only subfile when issued in it.
>
> Any comments? I would prepare a patch after confirmation here.
`thing-at-point-file-name-chars' is a good list of characters
allowable in filenames (maybe it won't work in some corner case but
should do the job in most cases). However I don't have a preference
between your regexp and `thing-at-point-file-name-chars'.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.
2017-02-01 11:20 GMT-08:00 Tassilo Horn : > Gosh, can you please clean up after me? I'm already in the bringing sick son > to bed business which might take a while. Done. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.
2017-02-01 10:29 GMT-08:00 Tassilo Horn : > Tassilo Horn writes: > >> Ikumi, I'll implement that now. Could you please check if it works as >> expected in the coming days? > > Pushed with commit d54e7472. The second argument of `local-variable-p' is mandatory in XEmacs ;-) Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.
Hi Tassilo, 2017-02-01 7:57 GMT+01:00 Tassilo Horn : > Do you know if XEmacs has some similar feature, i.e., a way to check > which variables have been set using file (or directory) local variables? If you want to check whether a variable was set locally in a XEmacs-compatible way you can use: (local-variable-p 'variable-name (current-buffer)) This is what is done in style/biblatex.el ;-) Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#22610: Auctex doesn't work with Atril (Mate's version of evince)
Hi Antoine, 2017-01-21 21:51 GMT+01:00 Antoine Levitt : > Same here, works on 1.16.1, you can close the ticket. Many thanks! > > Of course, in the meantime, the distribution I use (Linux Mint) has > decided to introduce a second fork of evince (!), called Xviewer, but I > gave up trying to follow and am just waiting for the dust to clear. Thank you for confirmation ;-) Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#22610: Auctex doesn't work with Atril (Mate's version of evince)
Hi Antoine, today I tried Atril again, version 1.16.1, and it seems that both forward and inverse search now work. Can you please confirm? If you do so, we can close this ticket. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24412: 11.89; Wrong DocTeX-mode
Hi Piet, 2016-09-12 11:55 GMT+02:00 Piet van Oostrum : > I want newline in a dtx buffer to automatically insert the % at the beginning > of the line. You have to set TeX-newline-function to an appropriate value. I > thought LaTeX-newline would be a good value, but that is not interactive. So > I ended up with: > (setq TeX-newline-function #'(lambda () (interactive) (LaTeX-newline))) > > Is there a better way? Or would I rather request LaTeX-newline to be made > interactive? I made `LaTeX-newline' interactive. Can this ticket be closed now? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24952: 11.89.7; Makeglossaries missing
Hi Ernst, 2016-11-16 5:46 GMT+01:00 Ernst Reissner : > This is more a feature request than a bugreport: They're fine ;-) > As index creation is supported invoking makeindex, > also glossary creation shall be supported invoking makeglossaries. I added a "Glossaries" entry to the default value of `TeX-command-list'. Thank you for the suggestion. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25447: 11.90.0; alltt environment should allow being extended in wrapper
Hi Jean-François,
2017-01-14 11:41 GMT+01:00 jfbu :
> Hi,
>
> \newenvironment{myalltt}
> {\begin{alltt}%
>\IamAllowedToDefineWrapperOfAllTT
>\ButFontificationByAucTeXIsProblematic
> }
> {\end{alltt}}
>
> causes fontification problem. I can use \alltt and \endalltt
> but this forces me to change TeX code for this issue.
>
> (alltt is not implemented like standard verbatim, the latter
> would indeed not allow the above kind of redefinition)
This is not limited to "alltt" but to any verbatim-like environment.
Possible workaround
--8<---cut here---start->8---
\newenvironment{myalltt}
{%
\begin{alltt}%
...
}
{\end{alltt}}
--8<---cut here---end--->8---
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
2017-01-12 20:08 GMT+01:00 jfbu :
> I get the script raising to work fine, but under the condition
> of typing explicitely braces, i.e.
>
> \( x^{y^{z^a_b}} \)
>
> does the expected thing from the docs after having set to
> multi-level the ‘font-latex-fontify-script’, but the thing
> about electric scripts does not seem to work
>
> \( x^y_z \) does not insert the braces while typing
> even with
>
> % Local variables:
> % TeX-electric-sub-and-superscript: t
> % End:
Does the equation "\( x^y_z \)" start at the beginning of the buffer?
`texmathp' cannot recognize math mode \(...\) starting at bob. In any
other place it should work fine. If this is not the culprit, please
open a new issue.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
2017-01-12 20:01 GMT+01:00 jfbu : > Le 12/01/2017 à 19:57, Mosè Giordano a écrit : >> >> 2017-01-12 19:50 GMT+01:00 jfbu : >>> >>> Hi Mosè, >> >> >> What is "^" bound to? Issue >> >> C-h k ^ >> > > ^ runs the command TeX-insert-sub-or-superscript (found in LaTeX-mode-map), > which is an interactive compiled Lisp function in ‘tex.el’. > > It is bound to _, ^. > > (TeX-insert-sub-or-superscript ARG) > > Insert typed key ARG times and possibly a pair of braces. > Brace insertion is only done if point is in a math construct and > ‘TeX-electric-sub-and-superscript’ has a non-nil value. Uh, I don't know what's happening here. Could you please open a new ticket? > try \input xintexpr.sty\relax\xinttheexpr 2^3^4\relax ;-) Cool! Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
2017-01-12 19:50 GMT+01:00 jfbu : > Hi Mosè, > > thanks but regarding > > Le 12/01/2017 à 19:37, Mosè Giordano a écrit : >> >> In any case I strongly suggest you to set >> `TeX-electric-sub-and-superscript' to t, I always find it very useful >> also for single character script (in that case braces are redundant, >> of course, but they improve readability, IMHO). > > > it does not work for me (the stuff on top of screenshot was typed > in after having set the variable, and no braces appeared, did I miss > something ?) What is "^" bound to? Issue C-h k ^ Bye, Mosè PS: double super- subscripts are not allowed in TeX ;-) ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
Hi Jean-François,
2017-01-12 8:38 GMT+01:00 jfbu :
> Hi All,
>
> in the attached screenshot with newly released 11.90, one sees
> a feature which I find a bit disturbing: all the subscripts look
> like they have a leading minus sign, where in fact it is the underscore
> character.
>
> Have you discussed that in the thread already ?
> (I read it back then but did not follow all details)
>
> I suppose this is expected result, and as my memory reboots
> on each 24h cycle, it may even have nothing to do with this thread
> and was like this for ages, but I come asking nevertheless.
>
> The foo^{\psi_n} is ok but all foo_{bar} get the underscore aligned
> with exact middle of brace which creates (from a distance and with an
> ageing user) this impression about minus signs everywhere.
Yes, the discussion about this issue started with this message:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25309#127 Indeed the
change of the face of caret and underscore was meant to address this
issue.
In any case I strongly suggest you to set
`TeX-electric-sub-and-superscript' to t, I always find it very useful
also for single character script (in that case braces are redundant,
of course, but they improve readability, IMHO).
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
2017-01-05 14:01 GMT+01:00 Tassilo Horn : > The problem was that the face/display specs for the script chars > replaced the existing specs (math and sub/superscript), thus they were > never shrunken. Now I prepend the spec which means that the shrinking > happens also for ^_ which are themselves part of a sub- or superscript. Very good! My problem is still there, but the different face is a nice compromise. Thank you! Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
2017-01-05 12:51 GMT+01:00 Mosè Giordano :
> In my opinion, the top of the caret should line up
> with the top of what it raises, see the "^{2}" in the text line below
> the equation. Of course, something similar for the underscore.
Thinking about this twice, this may not be the best solution, because
the caret could be too much high compared to the base of the power
(and the same for the underscore). There will be anyway a tension
between keeping the carte close to the base and to the exponent.
Something in the middle?
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
Hi Tassilo,
2017-01-05 11:11 GMT+01:00 Tassilo Horn :
>
> I think I came up with a solution: fontify the script characters
> themselves with a custom face.
I like this solution, I'm starting to love the multi-level mode
(though I don't think I'll personally use many nested scripts)!
Fontifying those characters differently from the rest of the equation
is really effective and does solve the issue you mentioned in
invisible mode.
However, I don't think it completely solves the problem I reported,
just works around it ;-) This is more evident in multi-level mode,
see the attached screenshot (I swear it's there this time!). The
caret is (almost always) in the wrong position, compared to the number
it is raising. In my opinion, the top of the caret should line up
with the top of what it raises, see the "^{2}" in the text line below
the equation. Of course, something similar for the underscore.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
2017-01-04 18:43 GMT+01:00 Tassilo Horn : > Anyway, my sense for aesthetics is very rudimentary so you have to > explain to me where the bug is. What I did, however, is that I changed > the default raise values from ±0.3 to ±0.5. So indeed the superscripts > are a bit more raised and the subscripts a bit more lowered. The bug, in my opinion, is that the "2" is slightly above of "^", and "3" is slightly below of "_". In particular the subscript is more problematic because it looks like it's written "-3" (ok, in my example there are braces, ideally remove them). My suggestion is just to put "^" and "_" at the same level as the scripts (as I think it was before, at least it looks like this). Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
2017-01-04 17:08 GMT+01:00 Mosè Giordano :
> Hi Tassilo,
>
> while trying to reproduce the problem reported by Gennady (I can
> confirm it), I noticed another glitch. Now the baseline of the script
> is slightly above (below) of "^" ("_"), see the attached screenshot
> (left: as it was before, right: as it is now).
Of course the attachment was not there :-)
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
Hi Tassilo,
while trying to reproduce the problem reported by Gennady (I can
confirm it), I noticed another glitch. Now the baseline of the script
is slightly above (below) of "^" ("_"), see the attached screenshot
(left: as it was before, right: as it is now).
Regarding the problem reported by Gennady, also before your latest changes, with
$1=x^$
the last "$" is raised, as it should be, but adding the "2" fixes the
position of "$" immediately.
Thanks,
Mosè
2017-01-04 13:52 GMT+01:00 Gennady Uraltsev :
> Hello Everyone,
>
> I was testing out this new mode and there seems still to be some small
> problem. The simplest case is as follows:
>
> write the following
>
> $1=x^2$
>
> in the standard order and make sure that electric $ mode is off i.e. the
> typing should look like this (with | being the cursor):
>
> |
> $|
> $1|
> $1=|
> $1=x|
> $1=x^|
> $1=x^2|
> $1=x^2$|
>
> Everything works fine. However let's try this order:
>
> |
> $|
> $1|
> $1=|
> $1=x|
> $1=x$|
> $1=x|$
> $1=x^|$
> $1=x^2|$
>
> Notice that $ is then "raised". Now erase the exponents by doing
> $1=x^2|$
> $1=x^|$
> $1=x^$
> The problem is that the closing $ is still raised.
>
>
> When I have more info I'll write more.
>
> Cheers,
>
> Gennady
>
>
> On 03/01/17 18:57, Mosè Giordano wrote:
>> 2017-01-03 16:27 GMT+01:00 Tassilo Horn :
>>> Ok, there's a new variable `font-latex-fontify-script-max-level' which
>>> defines up to which scriptification level the script faces are applied
>>> again (thereby causing the decrease in font size).
>>>
>>>> In my pixelated example, position of the baseline starts to be wrong
>>>> after the fifth nested script (but this depends on the font and its
>>>> size), maybe we can stop scaling after the ~4th nested script?
>>>
>>> A problem of the previous version of the feature was that the raise
>>> factors were just added up and didn't account for the fact that the font
>>> size also shrinks. In the current version, with each level the addition
>>> to the raise value gets smaller (about 80% of the previous addition).
>>
>> I think it's perfect now for most cases! Thank you so much.
>>
>> Bye,
>> Mosè
>>
>
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
2017-01-03 16:27 GMT+01:00 Tassilo Horn : > Ok, there's a new variable `font-latex-fontify-script-max-level' which > defines up to which scriptification level the script faces are applied > again (thereby causing the decrease in font size). > >> In my pixelated example, position of the baseline starts to be wrong >> after the fifth nested script (but this depends on the font and its >> size), maybe we can stop scaling after the ~4th nested script? > > A problem of the previous version of the feature was that the raise > factors were just added up and didn't account for the fact that the font > size also shrinks. In the current version, with each level the addition > to the raise value gets smaller (about 80% of the previous addition). I think it's perfect now for most cases! Thank you so much. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
Hi Tassilo,
2017-01-03 10:45 GMT+01:00 Tassilo Horn :
> Gennady Uraltsev writes:
>
>> Yep! Looks fantastic!
>>>
>>> Absolutely great. :-D
>
> Ok, great. Committed and pushed! I'm closing this bug then.
Thank you, this is amazing!
A couple of requests:
1) could you please mention this feature in doc/changes.texi?
2) is it possible to set a limit to scaling?
\(a^{b^{c^{d^{e^{f^{g^{h}}}\)
is hardly readable, see the attached screenshot (though it's uncommon
to have hyper-nested scripts). This is unreadble also in the output
document, but I think that the source code should always be readable.
In my pixelated example, position of the baseline starts to be wrong
after the fifth nested script (but this depends on the font and its
size), maybe we can stop scaling after the ~4th nested script?
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
2016-12-31 15:57 GMT+01:00 Gennady Uraltsev : > Hello, > > I use Emacs a lot but I am not very familiar with coding. During this > winter break I tried to look through the code base a bit to learn. > > The multi-level fontification was introduced by > Tassilo Horn with commit 513490f on 2015-09-03. Wow, I didn't even remember such change! My memory is failing :-( Tassilo, when/if you have time (I don't want to break your holidays ;-), could you please give a look at this? Thank you, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25309: 11.89.8; multi-level script fontification stacks incorrectly
Hi Gennady, 2016-12-31 15:12 GMT+01:00 Gennady Uraltsev : > Hello, > > I have discovered multi-level fontification of sub and superscripts. Honestly, I didn't even know this feature! > However it seems slightly broken. While the scaling of the text defined > in the face stacks correctly the displacement doesn't! Regarding this problem and the other ones you reported earlier, I don't think I'll have the time to fix them, but patches are always welcome ;-) > Thanks for your time and patience! I really appreciate the fantastic > piece of software you wrote. I have tried many LaTeX editors and AucTeX > is by far the best way to write. I'm just one of the many AUCTeX developers, but I'm sure we're all always glad to read such nice comments! Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24444: documentation bug
Hi Tyler, 2016-09-15 16:13 GMT+02:00 Tyler Smith : > Hi, > > The manual section "(auctex) Adding Macros" includes the following: > > 'TeX-arg-file' > Prompt for a filename in the current directory, and use it > without > the extension. > > This is not correct. TeX-arg-file returns the full file name, *with* the > extension. Fixed, thank you! Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24546: 11.89.5; preview-latex does not work with beamer TL2016
Hi Uwe, 2016-09-26 10:22 GMT+02:00 Uwe Brauer : > >> Hi Uwe, >> 2016-09-26 10:02 GMT+02:00 Uwe Brauer : > >> What do you expect to be previewed in a document where there is >> nothing to preview? If I add an equation, either inline or display, >> the preview is correctly generated. > > Ah I deleted the graphics. The problem is caused by the use of > beamer+graphics+plus some packages. > > I dig again in and report back Any news? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#23180: Still a problem
Hi Uwe, can we close this ticket? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25276: 11.89.8; xetex engine not work when master filename contains space
Hi Arash, > As a test, at a command prompt I can do > > xelatex -interaction=nonstopmode "\input" "foo bar.tex" > > and it works, but > > xelatex -interaction=nonstopmode "\input" '"foo bar.tex"' > > exits with: > > This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX) > (preloaded format=xelatex) > restricted \write18 enabled. > entering extended mode > LaTeX2e <2016/03/31> patch level 3 > Babel <3.9r> and hyphenation patterns for 67 language(s) loaded. > ! I can't find file `'"foo bar.tex"''. > <*> \input '"foo bar.tex"' > > (Press Enter to retry, or Control-Z to exit) > Please type another input file name > ! Emergency stop. > <*> \input '"foo bar.tex"' > > Does this help? > > Best, Arash > Not really, because it's seems logic to me that '"foo bar.tex"' isn't the intended file name. The problem is correctly quoting the file name on Windows. (shell-quote-argument (TeX-master-file)) doesn't seem to do the right thing on Windows. I don't know the details of quoting on Windows in general, and of Emacs on Windows in particular. You may try poking help-gnu-emacs or emacs-devel to get advices on this. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25276: 11.89.8; xetex engine not work when master filename contains space
Hi Qiang, 2016-12-27 8:52 GMT+01:00 Qiang Yin : > > I test the example "foo bar.tex" on Debian with Emacs 24.4. > > When run "M-: (shell-quote-argument （TeX-master-file)) RET" on "foo > bar.tex",it returns "foo\\ bar"; > and run the same command on "foo.tex" it returns "foo". The problem is only on Windows, not other operating systems ;-) Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25276: 11.89.8; xetex engine not work when master filename contains space
2016-12-26 18:59 GMT+01:00 Qiang Yin : > Hi Mosè, > > 1. When run on "foo bar.tex" it returns "\"foo bar\"". > 2. When run on "foo.tex" it returns "\"foo\"". Thank you. I cannot tell what's the difference and why it works in one case but not in the other. Sorry, I don't think I can personally do much on this, without a Windows box. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25276: 11.89.8; xetex engine not work when master filename contains space
Qiang or anybody using Windows,
can you please tell me what
M-: (shell-quote-argument (TeX-master-file)) RET
returns in a your "foo bar.tex" buffer? And what in a file's buffer
without spaces in its name? This is, more or less, the command used
in `TeX-command-expand' to build the compilation command.
Thank you,
Mosè
2016-12-26 17:25 GMT+01:00 Mosè Giordano :
> Hi Qiang,
>
> 2016-12-26 16:34 GMT+01:00 Qiang Yin :
>> Hi,
>> I prefer xetex as my default tex engine. But this will cause a AucTeX
>> bug when the master filename contains a space.
>>
>> The following is a minimal example. It contains only one master file "foo
>> bar.tex". Notice the filename contains a space. And the content of "foo
>> bar.tex" is just the following:
>>
>> \documentclass{article}
>> \begin{document}
>> Hello world
>> \end{document}
>> %%% Local Variables:
>> %%% mode: latex
>> %%% TeX-master: t
>> %%% TeX-engine: xetex
>> %%% End:
>>
>> Now if press C-c C-c to compile this file. AucTeX will return the
>> following error message:
>>
>> Running `LaTeX' on `foo bar' with ``xelatex -file-line-error --synctex=1
>> -interaction=nonstopmode "\input" ^"\^"foo bar.tex\^"^"''
>> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX)
>> (preloaded format=xelatex)
>> restricted \write18 enabled.
>> entering extended mode
>> LaTeX2e <2016/03/31> patch level 3
>> Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.
>> ! I can't find file `'"foo bar.tex"''.
>> <*> \input '"foo bar.tex"'
>>
>> (Press Enter to retry, or Control-Z to exit)
>> Please type another input file name
>> ! Emergency stop.
>> <*> \input '"foo bar.tex"'
>
> I cannot reproduce this on GNU/Linux:
>
> --8<---cut here---start->8---
> Running `LaTeX' on `foo bar' with ``xelatex -file-line-error
> --synctex=1 -interaction=nonstopmode "\input" \"foo\ bar.tex\"''
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016)
> (preloaded format=xelatex)
> restricted \write18 enabled.
> entering extended mode
> LaTeX2e <2016/03/31> patch level 3
> Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.
> (./foo bar.tex (/opt/texlive/2016/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
> (/opt/texlive/2016/texmf-dist/tex/latex/base/size10.clo))
> No file "foo bar".aux.
> [1] (./foo bar.aux) )
> Output written on foo bar.pdf (1 page).
> SyncTeX written on foo bar.synctex.gz.
> Transcript written on foo bar.log.
>
> TeX Output finished at Mon Dec 26 17:11:20
> --8<---cut here---end--->8---
>
> I see that you're running Emacs on Windows, maybe there is something
> special to be taken care of on that system. I find it strange that
> you experience this problem only with one engine: I didn't check it,
> but I thought that the expansion of file name doesn't depend on the
> selected engine.
>
> I'll try to have a look, but not using Windows, it's difficult for me.
> If someone else comes up with a solution, please chime in.
>
> Bye,
> Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#25276: 11.89.8; xetex engine not work when master filename contains space
Hi Qiang,
2016-12-26 16:34 GMT+01:00 Qiang Yin :
> Hi,
> I prefer xetex as my default tex engine. But this will cause a AucTeX
> bug when the master filename contains a space.
>
> The following is a minimal example. It contains only one master file "foo
> bar.tex". Notice the filename contains a space. And the content of "foo
> bar.tex" is just the following:
>
> \documentclass{article}
> \begin{document}
> Hello world
> \end{document}
> %%% Local Variables:
> %%% mode: latex
> %%% TeX-master: t
> %%% TeX-engine: xetex
> %%% End:
>
> Now if press C-c C-c to compile this file. AucTeX will return the
> following error message:
>
> Running `LaTeX' on `foo bar' with ``xelatex -file-line-error --synctex=1
> -interaction=nonstopmode "\input" ^"\^"foo bar.tex\^"^"''
> This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016/W32TeX)
> (preloaded format=xelatex)
> restricted \write18 enabled.
> entering extended mode
> LaTeX2e <2016/03/31> patch level 3
> Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.
> ! I can't find file `'"foo bar.tex"''.
> <*> \input '"foo bar.tex"'
>
> (Press Enter to retry, or Control-Z to exit)
> Please type another input file name
> ! Emergency stop.
> <*> \input '"foo bar.tex"'
I cannot reproduce this on GNU/Linux:
--8<---cut here---start->8---
Running `LaTeX' on `foo bar' with ``xelatex -file-line-error
--synctex=1 -interaction=nonstopmode "\input" \"foo\ bar.tex\"''
This is XeTeX, Version 3.14159265-2.6-0.6 (TeX Live 2016)
(preloaded format=xelatex)
restricted \write18 enabled.
entering extended mode
LaTeX2e <2016/03/31> patch level 3
Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.
(./foo bar.tex (/opt/texlive/2016/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/opt/texlive/2016/texmf-dist/tex/latex/base/size10.clo))
No file "foo bar".aux.
[1] (./foo bar.aux) )
Output written on foo bar.pdf (1 page).
SyncTeX written on foo bar.synctex.gz.
Transcript written on foo bar.log.
TeX Output finished at Mon Dec 26 17:11:20
--8<---cut here---end--->8---
I see that you're running Emacs on Windows, maybe there is something
special to be taken care of on that system. I find it strange that
you experience this problem only with one engine: I didn't check it,
but I thought that the expansion of file name doesn't depend on the
selected engine.
I'll try to have a look, but not using Windows, it's difficult for me.
If someone else comes up with a solution, please chime in.
Bye,
Mosè
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24951: 11.89.7; TeX-command-extra-options takes only last option into account.
Hi Ernst, do you have `TeX-auto-save' and `TeX-parse-self' variables set to non-nil? If so, try this: delete the autogenerated file (the file in the "auto/" subdirectoy and with the same basename of your master file and ".el" extension), then restart Emacs and reparse the LaTeX file with C-c C-n. Does this solve your issue? Bye, Mosè 2016-11-30 2:12 GMT+01:00 Mosè Giordano : > Hi Ernst, > > 2016-11-29 22:38 GMT+01:00 Ernst Reissner : >> So the blank between -recorder and -shell-escape seems to be ignored. >> How can this be? >> And how to explain that the behavior changed??? > > No idea, really, above all the fact that you're experiencing a > different problem now without having changed anything, I guess. Do > you have customizations related to AUCTeX in your init file? > > Bye, > Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24951: 11.89.7; TeX-command-extra-options takes only last option into account.
Hi Ernst, 2016-11-29 22:38 GMT+01:00 Ernst Reissner : > So the blank between -recorder and -shell-escape seems to be ignored. > How can this be? > And how to explain that the behavior changed??? No idea, really, above all the fact that you're experiencing a different problem now without having changed anything, I guess. Do you have customizations related to AUCTeX in your init file? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24989: 11.89; Wrong number of arguments: setq, 3
Hi Andrei, 2016-11-22 20:45 GMT+01:00 Andrei Sabelfeld : > Wrong number of arguments: setq, 3 This bug report is pretty... well... short. I guess you're experiencing the same problem reported here https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22417 (ie, you're loading the "subfigure" package in your document, triggering loading a bugged "subfigure.el" style file in Emacs), right? If so, I suggest you to update your AUCTeX package using ELPA, but I suspect you installed the package in another way. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24866: AucTeX not working on Emacs 25.1.1 for Mac
Hi Lars, 2016-11-19 20:57 GMT+01:00 Lars Eriksson : > Dear Mosè, > > Thank you for caring about this, and pointing me to git bisect. Sorry for > taking so long time to respond but I had to make a business trip to China > and did not have access to this computer for testing. Don't worry, thanks for the help! ;-) > I am now back and I > have now run a git bisect (for the first time in my life) and received the > following, results. > I have not analyzed what the difference is between the versions but it its > clear that it touches the preview… I do not know why it causes the error on > Mac... > > Best, > Lars > > > ~/Src/auctex $ git bisect good > 3fdeb4b8de31702d4c58b063cd9536284bb27ff7 is the first bad commit > commit 3fdeb4b8de31702d4c58b063cd9536284bb27ff7 > Author: Tassilo Horn > Date: Fri Aug 7 17:54:58 2015 +0200 > > Setup preview differently; fixes bug#21188 > > > > * latex.el (TeX-latex-mode): Call `LaTeX-preview-setup' > unconditionally instead of calling it from `LaTeX-mode-hook' which > breaks things if that hook is customized (bug#21188). > > > > * preview.el.in: Don't add `LaTeX-preview-setup' to > `LaTeX-mode-hook'. This was easy to guess, since it's the commit which introduced the function call, but a confirmation is useful anyway. @Tassilo, could you please have a look at this? I'm a bit confused by this problem, I can't see what's the culprit and why should be operating system-dependent :-/ Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24951: 11.89.7; TeX-command-extra-options takes only last option into account.
Hi Ernst, please don't write privately to me but push the "Reply all" button in order to send your message also to the bug tracker. Using the "Reply all" button is a good habit in mailing lists ;-) 2016-11-18 20:24 GMT+01:00 Ernst Reissner : > Hi Mosè, >> 2016-11-16 5:44 GMT+01:00 Ernst Reissner : >>> I set in my latex main file: >>> >>> %%% TeX-command-extra-options: "-src-specials -recorder -shell-escape" >>> >>> Nevertheless, when running the pdflatex compiler, >>> the only option I receive is -shell-escape, the last one. >> Does this happen only for one document or every documents? I mean, in >> every documents do you always have "-shell-escape" in the command use >> to compile the document, irrespective of the value of >> `TeX-command-extra-options'? In addition, what's the value of >> `LaTeX-command-style' option for you? > The command has option - shell-escape only if I specify this in > TeX-command-extra-options. > This is completely ok. > The problem is only, that if I specify more options, say in addition > -recorder, > then still *only* -shell-escape appears. > > I now removed the line TeX-command-extra-option. > When I restart emacs and load the tex-file, then of course, it does not > ask again on whether I accept -shell-escape, > but still it run latex with shell escape: > > Running `LaTeX' on `manualLatexMavenPlugin' with ``pdflatex > -file-line-error -shell-escape --synctex=1 -interaction=nonstopmode > "\input" manualLatexMavenPlugin.tex'' > This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) > (preloaded format=pdflatex) > \write18 enabled. > entering extended mode So, whatever the value of `TeX-command-extra-options' the command executed is always the same? > This is crazy, right? No, because if guess correctly, I suspect you customized `LaTeX-command-style'. What's the value of this option? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24951: 11.89.7; TeX-command-extra-options takes only last option into account.
Hi Ernst, 2016-11-16 5:44 GMT+01:00 Ernst Reissner : > I set in my latex main file: > > %%% TeX-command-extra-options: "-src-specials -recorder -shell-escape" > > Nevertheless, when running the pdflatex compiler, > the only option I receive is -shell-escape, the last one. Does this happen only for one document or every documents? I mean, in every documents do you always have "-shell-escape" in the command use to compile the document, irrespective of the value of `TeX-command-extra-options'? In addition, what's the value of `LaTeX-command-style' option for you? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24877: Feature request: let TeX-error-overview show warnings, but ignore them in TeX-next-error
Hi Clément, 2016-11-08 1:40 GMT+01:00 Clément Pit--Claudel : > On 2016-11-07 18:18, Mosè Giordano wrote: >> Before applying it, please have a look to the patch attached. Do you >> think it's ok? > > Looks perfect. Any reason to use `if` over `when`? Yes: laziness ;-) Patch installed, thank you for the suggestion! Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24866: AucTeX not working on Emacs 25.1.1 for Mac
Hi Lars, 2016-11-08 0:02 GMT+01:00 Lars Eriksson : > Hi Mosè, > > I have now tested AucTeX (from git) on Emacs 25.1-1 on Mac and I am sorry to > say that adding load paths did not help in my case. Same error, independent > of load path. I have tried both without and with the addition of one and both > of the following load paths before loading auctex.el > (add-to-list 'load-path > "/Applications/Emacs.app/Contents/Resources/site-lisp") > (add-to-list 'load-path > "/Applications/Emacs.app/Contents/Resources/site-lisp/auctex") > (load "auctex.el" nil t t) > > From the debugger output below I have found that the error is encountered > when it evaluates TeX-latex-mode() in the file latex.el. That's no surprise, since it's the only place where the function is called ;-) The point is that the function should be called only if it's available, but when it's called it turns out that it's not actually there. If you're familiar with git, can you please run git bisect in order to look for the offending revision? You can use "release_11_88" as good revision, and "release_11_89" as the bad one. Thanks, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24877: Feature request: let TeX-error-overview show warnings, but ignore them in TeX-next-error
Hi Clément, 2016-11-07 1:58 GMT+01:00 Clément Pit--Claudel : > On 2016-11-06 18:20, Mosè Giordano wrote: >> Hi Clément, > > Hi Mosè, > >>> […] It could say "no errors or warning to show; try >>> customizing `…'"? >> >> That's a sensible suggestion, thanks. Maybe we can conditionally >> add that suggestion when there are warnings/bad boxes. I can do >> this, but not right now, probably tomorrow or in the next few days. >> Feel free to ping me here if I miss to do it this week. > > Great, thanks! Before applying it, please have a look to the patch attached. Do you think it's ok? Bye, Mosè patch Description: Binary data ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24866: AucTeX not working on Emacs 25.1.1 for Mac
2016-11-07 15:40 GMT+01:00 Lars Eriksson : > Hi Mosè, > > Thanks for being engaged in this. > > Are you working on a Mac and did you try to start it without the load path > added? > > I have a configuration that works (Au 11.88 and Em 24.5) so I will need to > uninstall and reinstall and do the testing, anyway I will test tonight for > the benefit of the community... No, I don't use Mac OS, but I'd surprised to discover this is an operating-system-related issue, the setup is supposed to be the same on all *nix systems. Please, keep the 24...@debbugs.gnu.org address in the CC list when replying to this thread (simply hit the "Reply all" button), so that everybody can follow it. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24866: AucTeX not working on Emacs 25.1.1 for Mac
Hi Lars, I tried to reproduce your problem, to no avail. I actually used the following configuration line (I use GNU/Linux): ./configure --with-lispdir=/usr/local/share/emacs/site-lisp \ --with-auto-dir=/usr/local/share/emacs/site-lisp/auctex/auto \ --infodir=/usr/local/share/emacs/info --without-texmf-dir and added to my init file: (add-to-list 'load-path "/usr/local/share/emac/site-lisp") (load "auctex.el" nil t t) When I open *TeX files, I get no error. Thus, you should try to debug it yourself. An indication: is "$EMACSMAIN/site-lisp/auctex" in your `load-path'? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24866: AucTeX not working on Emacs 25.1.1 for Mac
Hi Lars, 2016-11-05 12:42 GMT+01:00 Lars Eriksson : > A correction: > I made a mistake in my test with the 24.5, I was too quick on the keyboard > With the auctex error there is no syntax highlighting. I installed 24.5 and > AucTeX and opened emacs with a latex file and got syntax highlighting so I > believed auctex was loaded but it was not, at the time of me sending the > mail. Some more testing showed that my Mac had started Emacs from the dmg > file that was still open at the time of testing and only loaded the standard > latex mode and gave me syntax highlighting and I jumped to the conclusion > that all was working… But when the dmg was unmounted AucTeX was not working. > > So the latest AucTeX-build did not work on 24.5…. > I later tried the old Au11.89 and Em 24.5 without success (same error) so I > went for Au 11.88 and Em 24.5 and can confirm that this works for me. > I have AucTex in the distribution place > /Applications/Emacs.app/Contents/Resources/site-lisp > and The source tree of AUCTeX has been changed in 11.89, so in principle it makes sense that you actually experience the problem with version 11.89 but not 11.88. What looks strange to me is that the change actually simplified things moving all files to the same directory. I'll try to reproduce your issue. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24877: Feature request: let TeX-error-overview show warnings, but ignore them in TeX-next-error
Hi Clément, 2016-11-04 17:00 GMT+01:00 Clément Pit--Claudel : > Hi all, > > I just found about TeX-error-overview, but when I first tried to use it it > just complained that there were "no errors or warning to show". Reading > through the implementation, I realized that it filters warnings using > TeX-error-list-skip-warning-p, which itself excludes all warnings by default > (maybe the message should be changed? It could say "no errors or warning to > show; try customizing `…'"? That's a sensible suggestion, thanks. Maybe we can conditionally add that suggestion when there are warnings/bad boxes. I can do this, but not right now, probably tomorrow or in the next few days. Feel free to ping me here if I miss to do it this week. > Also, the error list has a menu that allows me to change what kind of errors > are displayed but it's useless here: AucTeX errors out instead of showing an > empty list when there's nothing to display) Sorry, I don't get what you mean here. > I found this default surprising, until I realized that it's also used for > TeX-next-error (and it makes a lot of sense to jump to errors first, instead > of warnings). So now I have my own wrapper that binds TeX-debug-warnings and > TeX-debug-bad-boxes to t around a call to TeX-error-overview; that's not very > user-friendly. > > Maybe we need separate parameters for the error list and for the next-error > function? I don't usually want to browse through warnings if there are > errors, but I seldom want to see a list of only errors. Another option would > be to show all warnings in the error list when there are no errors. > > In any case, I think it would make sense to have a different default for the > errors and warnings list and for the next-error function. I don't quite agree on this. I think there are already many options available in this regard, I fear that adding even more complexity (different behavior for `TeX-next-error` and `TeX-erorr-overview`) is going to confuse users, that tend no to read documentation at all (and it seems you confirmed this suspect ;-). I could agree on changing the defaults of `TeX-debug-warnings' and `TeX-debug-bad-boxes' (I do it in my init file), but I'm personally against duplicating options for the two error reporting tools. If instead you truly believe this is a good idea, please start a discussion at auctex-de...@gnu.org so that other people can participate, bug tracker is not a good place for this stuff. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
bug#24866: AucTeX not working on Emacs 25.1.1 for Mac
Hi Lars, 2016-11-03 12:54 GMT+01:00 Lars Eriksson : > Hi, > > Might be Emacs and not AucTeX that cause the problems but it was AucTeX that > triggered my problems, and I wanted to make you aware... > > I have a clean installation of Emacs for Mac 25.1.1 and pulled a fresh > auctex from github (see script below). > In my .emacs I have reduced everything to to (load "auctex.el" nil t t) > When I try to open a LaTeX-file I get the message: I see that you're passing to configure an explicit --with-lispdir, did you add to your init file the line (add-to-list 'load-path "~/elisp") before loading auctex.el, as explained in the manual? Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org https://lists.gnu.org/mailman/listinfo/bug-auctex
