Re: TeX-documentation-texdoc
Great, it works now! It opens the requested file in the viewer and gives an
error message if it does not exist. (Well, it often opens a file even if I give
it a nonsensical string, like "d", which opens the documentation for
baskervaldadf -- but I assume that's a texdoc thing.)
All the best,
Greg
---
On Tue 24 Jan 2023 at 06:27 Ikumi Keita wrote:
> >>>>> Greg Bognar writes:
> > 1. Unfortunately, the new function definition below does not work with
> > okular. Same problem as before.
>
> Too bad. :-)
>
> > 2. All of the environment variables PDFVIEWER, PDFVIEWER_texdoc,
> > TEXDOCVIEW_pdf, and TEXDOC_VIEWER_PDF have an empty value.
>
> Thank you. It seems that the reported behavior originates from okular's
> own nature.
>
> Then can you test the code at the last of this message?
>
> [Rationale] The reason that `TeX-documentation-texdoc' tries hard to
> collect and show the output from Texdoc is that the exit code wasn't
> meaningful once[1]. However, recent Texdoc is improved to return
> non-zero exit code when it can't find documentation for the given
> keyword[2].
>
> Thus I think that AUCTeX need not collect the output now; it just has to
> look at the exit code. We can use `call-process' (with `executable-find'
> test in case that Texdoc isn't available) to run Texdoc.
>
> This has a drawback that the user who sticks to older TeX Live
> distribution isn't notified at all when the given keyword didn't match
> any documentation, but I expect it's permissible. Mosè, what do you
> think about it?
>
> Regards,
> Ikumi Keita
> #StandWithUkraine #StopWarInUkraine
>
> [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28905#17
> [2] https://tug.org/texdoc/doc/texdoc.man1.pdf
>
> --
> (defun TeX-documentation-texdoc (&optional arg)
> "Run texdoc to read documentation.
>
> Prompt for selection of the package of which to show the documentation.
>
> If called with a prefix argument ARG, after selecting the
> package, prompt for selection of the manual of that package to
> show."
> (interactive "P")
> (let ((pkg (thing-at-point 'symbol))
> buffer list doc)
> ;; Strip off properties. XXX: XEmacs doesn't have
> ;; `substring-no-properties'.
> (set-text-properties 0 (length pkg) nil pkg)
> (setq pkg (TeX-read-string "View documentation for: " pkg))
> (unless (zerop (length pkg))
> (if arg
> ;; Called with prefix argument: run "texdoc --list --nointeract
> "
> (progn
> ;; Create the buffer, insert the result of the command, and
> ;; accumulate the list of manuals.
> (with-current-buffer (get-buffer-create
> (setq buffer (format "*texdoc: %s*" pkg)))
> (erase-buffer)
> (insert (shell-command-to-string
>(concat "texdoc --list --nointeract " pkg)))
> (goto-char 1) ; No need to use `point-min' here.
> (save-excursion
> (while (re-search-forward
> ;; XXX: XEmacs doesn't support character classes in
> ;; regexps, like "[:alnum:]".
> "^ *\\([0-9]+\\) +\\([-~/a-zA-Z0-9_.${}#%,:\\
> ()]+\\)" nil t)
> (push (cons (match-string 1) (match-string 2)) list
> (unwind-protect
> (cond
> ((null (executable-find "texdoc"))
> ;; Note: `shell-command-to-string' uses shell, only
> ;; `call-process' looks at `exec-path', thus only here makes
> ;; sense to use `executable-find' to test whether texdoc is
> ;; available.
> (message "texdoc not found"))
> (list
> ;; Go on if there are manuals listed: show the buffer,
> prompt
> ;; for the number of the manual, then run
> ;; texdoc --just-view
> (TeX-pop-to-buffer (get-buffer buffer))
> (condition-case nil
> (when (setq doc
> (cdr (assoc (TeX-read-string "Please enter \
> the number of the file to view, anything else to skip: ") list)))
> (call-process "texdoc"
Re: TeX-documentation-texdoc
Hi Ikumi,
1. Unfortunately, the new function definition below does not work with okular.
Same problem as before.
2. All of the environment variables PDFVIEWER, PDFVIEWER_texdoc, TEXDOCVIEW_pdf,
and TEXDOC_VIEWER_PDF have an empty value.
All the best,
Greg
---
On Mon 23 Jan 2023 at 08:33 Ikumi Keita wrote:
> Hi Greg,
>
> >>>>> Greg Bognar writes:
> > Your code works! So yes, your commit harmed okular in some way.
>
> Thank you. That's a bad news for me :-)
>
> > Where do we go from here?
>
> Then we have to find out the way compatible for both okular and evince.
> Unfortunately, the old code is bad for evince; it still blocks emacs
> until the user quits evince as described in bug#28905[1].
>
> [1] https://debbugs.gnu.org/28905
>
> 1. Can you please test the following code, then? This uses
>`start-process' instead of `start-process-shell-command', as suggested
>by Mosè in the thread of [1].
> --
> (defun TeX-documentation-texdoc (&optional arg)
> "Run texdoc to read documentation.
>
> Prompt for selection of the package of which to show the documentation.
>
> If called with a prefix argument ARG, after selecting the
> package, prompt for selection of the manual of that package to
> show."
> (interactive "P")
> (let ((pkg (thing-at-point 'symbol))
> buffer list doc)
> ;; Strip off properties. XXX: XEmacs doesn't have
> ;; `substring-no-properties'.
> (set-text-properties 0 (length pkg) nil pkg)
> (setq pkg (TeX-read-string "View documentation for: " pkg))
> (unless (zerop (length pkg))
> (if arg
> ;; Called with prefix argument: run "texdoc --list --nointeract
> "
> (progn
> ;; Create the buffer, insert the result of the command, and
> ;; accumulate the list of manuals.
> (with-current-buffer (get-buffer-create
> (setq buffer (format "*texdoc: %s*" pkg)))
> (erase-buffer)
> (insert (shell-command-to-string
>(concat "texdoc --list --nointeract " pkg)))
> (goto-char 1) ; No need to use `point-min' here.
> (save-excursion
> (while (re-search-forward
> ;; XXX: XEmacs doesn't support character classes in
> ;; regexps, like "[:alnum:]".
> "^ *\\([0-9]+\\) +\\([-~/a-zA-Z0-9_.${}#%,:\\
> ()]+\\)" nil t)
> (push (cons (match-string 1) (match-string 2)) list
> (unwind-protect
> (cond
> ((null (executable-find "texdoc"))
> ;; Note: `shell-command-to-string' uses shell, only
> ;; `call-process' looks at `exec-path', thus only here makes
> ;; sense to use `executable-find' to test whether texdoc is
> ;; available.
> (message "texdoc not found"))
> (list
> ;; Go on if there are manuals listed: show the buffer,
> prompt
> ;; for the number of the manual, then run
> ;; texdoc --just-view
> (TeX-pop-to-buffer (get-buffer buffer))
> (condition-case nil
> (when (setq doc
> (cdr (assoc (TeX-read-string "Please enter \
> the number of the file to view, anything else to skip: ") list)))
> (call-process "texdoc" nil 0 nil "--just-view" doc))
> ;; Exit gently if a `quit' signal is thrown.
> (quit nil)))
> (t (message "No documentation found for %s" pkg)))
> ;; In any case quit-and-kill the window.
> (when (get-buffer-window buffer)
> (quit-window t (get-buffer-window buffer)
> ;; Called without prefix argument: just run "texdoc --view " and
> ;; show the output, so that the user is warned in case it doesn't find
> ;; the documentation or "texdoc" is not available.
> (message "%s"
> ;; The folowing code to the end of `defun' used to be
> ;; just
> ;; (shell-command-to-string (concat "texdoc --view "
Re: TeX-documentation-texdoc
Hi Ikumi,
Your code works! So yes, your commit harmed okular in some way. Where do we go
from here?
All the best,
Greg
---
On Sun 22 Jan 2023 at 10:37 Ikumi Keita wrote:
>
> Hi Greg,
>
> >>>>> Greg Bognar via General discussion about AUCTeX writes:
> > It turns out that C-u C-c? works: it opens a buffer with a list of related
> > files
> > and then opens the selected one in my PDF viewer (okular). It's only when I
> > call `TeX-documentation-texdoc' without a prefix argument that okular seems
> > to
> > be started (a startup notification appears in the panel), but then
> > disappears
> > and nothing happens.
>
> > texdoc itself has no problem starting the PDF viewer, and it seems all
> > `TeX-documentation-texdoc' does is calling it. I don't understand why it
> > works
> > with a prefix argument but not without one.
>
> That's because `TeX-documentation-texdoc' is written to behave in such a
> way:
> ,
> | (defun TeX-documentation-texdoc (&optional arg)
> | "Run texdoc to read documentation.
> | [...]
> | If called with a prefix argument ARG, after selecting the
> | package, prompt for selection of the manual of that package to
> | show."
> | [...]
> | (if arg
> | ;; Called with prefix argument: run "texdoc --list --nointeract
> "
> | [...]
> | (call-process "texdoc" nil 0 nil "--just-view" doc))
> | [...]
> | ;; Called without prefix argument: just run "texdoc --view "
> and
> | ;; show the output, so that the user is warned in case it doesn't
> find
> | ;; the documentation or "texdoc" is not available.
> | [...]
> | (process (start-process-shell-command
> | "Doc view" standard-output
> | (concat "texdoc --view " pkg
> | [...]
> `
>
> The difference is that it calls texdoc by `call-process' if prefix
> arugment is given while by `start-process-shell-command' without prefix
> argument.
>
> By the way, I remember there was a similar bug report[1] before. In that
> report, the PDF viewer was okular, too. So I suspect that AUCTeX has
> something potentially inconsistent with okular.
>
> [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40577
>
> Can you test whether the following code works for you? This was used
> before my commit mentioned in [1]. I'd like to know whether my commit
> harmed okular or not.
>
> Regards,
> Ikumi Keita
> #StandWithUkraine #StopWarInUkraine
>
> --
> (defun TeX-documentation-texdoc (&optional arg)
> "Run texdoc to read documentation.
>
> Prompt for selection of the package of which to show the documentation.
>
> If called with a prefix argument ARG, after selecting the
> package, prompt for selection of the manual of that package to
> show."
> (interactive "P")
> (let ((pkg (thing-at-point 'symbol))
> buffer list doc)
> ;; Strip off properties. XXX: XEmacs doesn't have
> ;; `substring-no-properties'.
> (set-text-properties 0 (length pkg) nil pkg)
> (setq pkg (TeX-read-string "View documentation for: " pkg))
> (unless (zerop (length pkg))
> (if arg
> ;; Called with prefix argument: run "texdoc --list --nointeract "
> (progn
> ;; Create the buffer, insert the result of the command, and
> ;; accumulate the list of manuals.
> (with-current-buffer (get-buffer-create
> (setq buffer (format "*texdoc: %s*" pkg)))
> (erase-buffer)
> (insert (shell-command-to-string
> (concat "texdoc --list --nointeract " pkg)))
> (goto-char 1) ; No need to use `point-min' here.
> (save-excursion
> (while (re-search-forward
> ;; XXX: XEmacs doesn't support character classes in
> ;; regexps, like "[:alnum:]".
> "^ *\\([0-9]+\\) +\\([-~/a-zA-Z0-9_.${}#%,:\\ ()]+\\)"
> nil t)
> (push (cons (match-string 1) (match-string 2)) list
> (unwind-protect
> (cond
>((null (executable-find "texdoc"))
> ;; Note: `shell-c
Re: TeX-documentation-texdoc
It turns out that C-u C-c? works: it opens a buffer with a list of related files and then opens the selected one in my PDF viewer (okular). It's only when I call `TeX-documentation-texdoc' without a prefix argument that okular seems to be started (a startup notification appears in the panel), but then disappears and nothing happens. texdoc itself has no problem starting the PDF viewer, and it seems all `TeX-documentation-texdoc' does is calling it. I don't understand why it works with a prefix argument but not without one. --- On Fri 20 Jan 2023 at 14:55 Greg Bognar wrote: > Hi, > > When I run `TeX-documentation-texdoc' (from the menu or with C-c ?), nothing > happens. The mouse pointer does turn into busy, but it stops after a while. > Nothing is written to *Messages* or to .xsession-errors. > > The texdoc command works from the terminal, opening a PDF viewer with the > requested document. > > I'm not sure whether this is an AUCTeX, Emacs, or window manager issue. Any > ideas how I could find out what the problem is? > > All the best, > Greg
Re: TeX-documentation-texdoc
I forgot to mention that I tried that too. It works. It prints Icon theme "gnome" not found. Icon theme "gnome" not found. Icon theme "gnome" not found. ... but opens the requested document in a PDF viewer. It's only when I try TeX-documentation-texdoc that I have the problem. --- On Fri 20 Jan 2023 at 15:52 David Kastrup wrote: > Greg Bognar via General discussion about AUCTeX writes: > > Hi, > > > > When I run `TeX-documentation-texdoc' (from the menu or with C-c ?), nothing > > happens. The mouse pointer does turn into busy, but it stops after a while. > > Nothing is written to *Messages* or to .xsession-errors. > > > > The texdoc command works from the terminal, opening a PDF viewer with the > > requested document. > > > > I'm not sure whether this is an AUCTeX, Emacs, or window manager issue. Any > > ideas how I could find out what the problem is? > > Try M-x shell RET and run texdoc from _that_ command line. That should at > least carry around some of the environment that TeX-documentation-texdoc is > working with. If it fails, you'll probably get some info in the Emacs buffer > used as terminal. > > -- > David Kastrup
TeX-documentation-texdoc
Hi, When I run `TeX-documentation-texdoc' (from the menu or with C-c ?), nothing happens. The mouse pointer does turn into busy, but it stops after a while. Nothing is written to *Messages* or to .xsession-errors. The texdoc command works from the terminal, opening a PDF viewer with the requested document. I'm not sure whether this is an AUCTeX, Emacs, or window manager issue. Any ideas how I could find out what the problem is? All the best, Greg
Re: Problem after upgrading to 13.1.3
Hi Ikumi and Arash, Thanks for the pointer. I think I understand what the problem was. When the issue started, I removed the new AUCTeX installation and re-installed it through the Emacs package manager to make sure no old version remained. But I also had a MELPA package called latex-extra installed, which depends on AUCTeX. I suspect the package manager did not actually delete AUCTeX but kept it around as a dependency -- and it never warned me about this. Eventually, I removed both AUCTeX and latex-extra and reinstalled AUCTeX only, and the problem went away. I looked at latex-extra and it requires tex-buf.el. So the problem seems to be that Emacs loaded a file with the new AUCTeX but then latex-extra could not be loaded and that lead to the weird behavior. The issue is already reported: https://github.com/Malabarba/latex-extra/issues/35 To be honest, I have not even used latex-extra's functionality. It was just an old package lying around... All the best, Greg --- On Thu 14 Jul 2022 at 09:23 Ikumi Keita wrote: > > Hi Greg, > > I don't use use-package, so I just state some observations which seem > relevant. > > >>>>> Greg Bognar via General discussion about AUCTeX writes: > > When I try to change the mode of the file by M-x LaTeX-mode, I get an error: > > >Cannot open load file: No such file or directory, tex-buf > > That strongly suggests that there remains older version of AUCTeX. In > recent commit, tex-buf.el was merged into tex.el. I guess that older one > is conflicting with newer one. > > > M-x describe-mode tells me: > > >Fundamental mode defined in `tex-mode.el': > > That's very strange. tex-mode.el actually has no definition for > Fundamental mode. > > Perhaps deleting AUCTeX once and installing again might help. > > Regards, > Ikumi Keita > #StandWithUkraine #StopWarInUkraine
Problem after upgrading to 13.1.3
Hi,
I've just upgraded to 13.1.3 from ELPA. I'm on Emacs 27.1.
When I open a LaTeX file, it opens in something called Fundamental mode. But I
do actually get font-locking and the basic AUCTeX menus, but none of my
customizations seem to have loaded. C-c C-c asks for the master file, even
though TeX-master is set in the file-local variables. M-x describe-mode tells
me:
Fundamental mode defined in `tex-mode.el':
This function has :override advice: `TeX-latex-mode'.
I use use-package to load AUCTeX:
(use-package tex
:ensure auctex
:defer t
:mode ("\\.tex\\'" . LaTeX-mode)
[...]
When I try to change the mode of the file by M-x LaTeX-mode, I get an error:
Cannot open load file: No such file or directory, tex-buf
My setup has worked without any problems before the upgrade. It seems
use-package does not load AUCTeX properly, although this is the way recommended
in the manual. I should also say I have a cryptic comment in my init file:
:ensure auctex ;FIXME: cannot be installed automatically
But I can't remember what problem I was trying to fix.
Does anyone who uses use-package have any advice on how to get AUCTeX working
again?
All the best,
Greg
Re: Inserting beamer frames
[...]
> > But when I try to write a function to use in LaTeX-after-insert-env-hook, I
> > stumble. [...]
> > I'm probably making some elementary mistake...
>
> No, it was me. I had a brief look at beamer.el as I made that
> suggestion. Looking closer, beamer.el defines:
>
> '("frame" (lambda (env &rest ignore)
> (let ((title (TeX-read-string "(Optional) Title: " nil
>'LaTeX-beamer-frametitle-history)))
>(LaTeX-insert-environment env)
>(unless (zerop (length title))
> (save-excursion
>(LaTeX-find-matching-begin)
>(end-of-line)
>(LaTeX-newline)
>;; Indent the next macro insertion and don't
>;; rely on the fill-function to do it:
>(indent-according-to-mode)
>(insert (format "\\frametitle{%s}" title))
>;; This works because \frametitle is a
>;; paragraph command.
>(when auto-fill-function
> (backward-char)
> (LaTeX-fill-paragraph)))
>
> `LaTeX-after-insert-env-hook' is called at the end of
> `LaTeX-insert-environment', \frametitle is inserted afterwards. Alas,
> any function added to `LaTeX-after-insert-env-hook' doesn't see that
> later insertion and would fail. Therefore the functions above.
Yes, I suspected something like this was happening. I ended up adopting
Mandar's suggestion of writing a beamer.el file and placing it in my
TeX-style-private directory (I think that's the one I need). This has the
advantage that I can format the frame insertion the way I want and don't need to
issue any commands to fix the formatting.
Thanks everyone!
Re: Inserting beamer frames
> > Yes, that's what I thought. Is there a way to, say, copy and modify that > > definition and add it as a new environment? E.g., calling `myframe' that > > inserts the frame with the customized formatting? > > Yes, you could do that, but I suggest to write a function which searches > back in the environment for \frametitle and then deletes any white > spaces/newlines to get the desired result. You could the add that > function to `LaTeX-after-insert-env-hook' in your init file like this: > > (with-eval-after-load "beamer" > (add-hook 'LaTeX-after-insert-env-hook #'your-function t)) > > Do you feel comfortable to write a `your-function'? Thanks for the suggestions. I wanted to try Arash's idea first. But I'm very incompetent in emacs-lisp. I can write an interactive function that seems to work: (defun my-frame-title-fix () "Fix the formatting of Beamer frame titles." (interactive) (save-excursion (previous-line) (forward-char) (when (string-equal "frametitle" (thing-at-point 'word 'no-properties)) (join-line) (delete-horizontal-space But when I try to write a function to use in LaTeX-after-insert-env-hook, I stumble. (defun my-hook-frame-title-fix (env start end) "Fix the formatting of Beamer frame titles." (save-excursion (goto-char start) (forward-to-indentation 1) (forward-char) (what-cursor-position) ;this shows we got to the right place, over "f" )) But this does not work: (defun my-hook-frame-title-fix (env start end) "Fix the formatting of Beamer frame titles." (save-excursion (goto-char start) (forward-to-indentation 1) (forward-char) (when (string-equal "frametitle" (thing-at-point 'word 'no-properties)) (join-line) (delete-horizontal-space I'm probably making some elementary mistake... All the best, Greg
Re: Inserting beamer frames
Hi Arash,
> Greg Bognar via General discussion about AUCTeX writes:
>
> > Hi, when I insert a new frame in a Beamer document, C-c C-e asks me for the
> > title and then inserts a frame this way:
> >
> > \begin{frame}
> > \frametitle{My title}
> >
> > \end{frame}
> >
> > I would prefer to format my frames like this:
> >
> > \begin{frame}\frametitle{My title}
> >
> > \end{frame}
> >
> > Is there a user option I can change?
>
> No, this is hard coded in beamer.el. Check the definition here[1] if
> you're interested in the details.
>
> Footnotes:
> [1] http://git.savannah.gnu.org/cgit/auctex.git/tree/style/beamer.el#n146
Yes, that's what I thought. Is there a way to, say, copy and modify that
definition and add it as a new environment? E.g., calling `myframe' that
inserts the frame with the customized formatting?
All the best,
Greg
Inserting beamer frames
Hi, when I insert a new frame in a Beamer document, C-c C-e asks me for the
title and then inserts a frame this way:
\begin{frame}
\frametitle{My title}
\end{frame}
I would prefer to format my frames like this:
\begin{frame}\frametitle{My title}
\end{frame}
Is there a user option I can change? I found information in the manual on how
to add support for new environments, but not how to reformat the way they are
inserted.
All the best,
Greg
Inserting comments
Hi,
I'm working on a document in which I use the comment package. The package is
supported by AUCTeX in comment.el. When I open the file, text between
\begin{comment} and \end{comment} is nicely fontified with the comment face.
The comment package has a quirk that it requires that \begin{comment} and
\end{comment} be placed at the beginning of the line. However, sometimes I want
to put comments between items in a list. But C-c C-e (`LaTeX-environment')
still indents the environment (as it should; IMHO the quirk is really a bug).
Nevertheless, is there a way to teach it not to do that?
It's not a big deal but sometimes I keep on commenting list items and
momentarily forget about the quirk and then get puzzled why my document didn't
compile before I remember.
All the best,
Greg
Re: cannot get AUCTeX to work
On Sat 9 Jan 2021 at 17:18 Joost Kremers wrote: > I do: > > ``` > (use-package tex-site > :ensure auctex > :config ...) > ``` > > Before use-package, before package.el even, `(require 'tex-site)` was the way > to > load AUCTeX, so I kept `tex-site` when I switched to use-package. > > Perhaps it would be a good idea to add an example `use-package` declaration to > the "Quick Start" section of the manual? Yes, but what *is* the right way? For instance, probably because I add to `LaTeX-mode-hook' in my :init declaration, using `(use-package tex-site' gives me (among others) the following error: Error (use-package): tex-site/:catch: Symbol's value as variable is void: LaTeX-mode-map So in my experience if you want to customize LaTeX-mode, you have to use `(use-package latex' to make sure latex.el is loaded. But perhaps I'm doing it the wrong way.
Re: cannot get AUCTeX to work
> Pastiche P writes:
>
> The error is gone, but I'm not sure AUCTeX itself is properly loaded. E.g.,
> the command LaTeX-section is undefined. Or perhaps I'm misunderstanding
> something?
In my experience, you need to do
(use-package latex
:ensure auctex
:mode ("\\.tex\\'" . LaTeX-mode)
:init (...)
:config (setq TeX-auto-save t
TeX-parse-self t
etc...))
This will load all the other libraries that latex.el requires.
I'm surprised by Tassilo's suggestion as tex-mode.el is not part of AUCTeX. It
is the built-in (La)TeX mode for Emacs -- isn't it?
> On Sat, 9 Jan 2021 at 11:18, Tassilo Horn wrote:
>
> > Pastiche P writes:
> >
> > Hi Pastiche,
> >
> > > I just installed AUCTeX 13.0.1 using M-x list-packages. This is Emacs
> > > 27.1 under Windows.
> > >
> > > I put this in my config:
> > >
> > > (use-package tex
> > > :ensure auctex
> > > :config
> > > (setq TeX-auto-save t)
> > > (setq TeX-parse-self t))
> > >
> > > Whenever I open a *.tex file, I get
> > >
> > > Debugger entered--Lisp error: (void-function TeX-latex-mode)
> >
> > Please try this use-package spec:
> >
> > (use-package tex-mode
> > :ensure auctex
> > :config
> > (setq TeX-auto-save t)
> > (setq TeX-parse-self t))
> >
> > Does that work? It does for me.
> >
> > Bye,
> > Tassilo
Re: TeX-next-error log buffer
> > Ikumi Keita writes: > > Colin Baxter writes: > > > When the error is corrected and the file is re-compiled, the log buffer is > > > updated with an echoed message. The log buffer is not deleted and on every > > > compilation thereafter the echoed update-message is again displayed. > > > That doesn't occur for me. My emacs opens the log file in read-only > > buffer and doesn't pay attention whether the log file is updated or not. > > Could you provide more detail? > > Well, this is most embarrassing. I find I cannot reproduce the effect and > indeed the log file behaves exactly as you stated. I will watch things > carefully and report back if I can reproduce it. In the meantime, please > accept my apologies for wasting your time. Perhaps I misundertood, but I thought Colin meant: for some TeX errors, AUCTeX opens the log file that TeX creates, and it is reverted on each subsequent TeX run, resulting in a message in the echo area which is indeed annoying. That is, there are two buffers involved: the *TeX Help* buffer with the error message, which is a read-only buffer and is updated without any echoed message; and the .log buffer, which is a file read from disk, and changing it results in an echoed message. (Assuming you have auto-revert mode enabled.) If this is indeed what happens, one option is to set `auto-revert-verbose' to nil, another is to add fundamental-mode (in which the log file is opened) to `global-auto-revert-ignore-modes'. Again, unless I misunderstood what the problem is in the first place.
Re: TeX-style-path
On Fri 11 Dec 2020 at 20:56 Arash Esbati wrote:
> Greg Bognar via General discussion about AUCTeX writes:
> > In my config, I set the values for TeX-auto-global, TeX-auto-private,
> > TeX-auto-local, TeX-style-private, and TeX-style-local variables.
> > TeX-style-path is constructed from these.
> >
> > So I have
> >
> > (use-package latex
> > :ensure auctex
> > :mode ("\\.tex\\'" . LaTeX-mode)
> > [...]
> > :config
> > [...]
> > TeX-auto-global (concat user-cache-directory "autoparse")
> > [etc]
> >
> > Is this the right way to do it? And why am I getting the default values?
>
> I don't use `use-package' so my comments might be off. First, I think
> Tassilo's suggestion is good wrt use `:init' instead of `:config'.
Yes, Tassilo's suggestion results in the right value for `TeX-style-path', but
weirdly, C-h v now says:
Value
("~/.cache/emacs/autoparse" "/home/greg/.emacs.d/elpa/auctex-12.3.1/style"
"~/.cache/emacs/auctex")
Original Value
("~/.cache/emacs/autoparse" "/home/greg/.emacs.d/elpa/auctex-12.3.1/style"
"~/.cache/emacs/auctex")
So Emacs thinks my modifications were both the original and the customized
values. I'd love to understand why that is.
> Looking at manual, you should also do
>
> (use-package tex ; not latex
> :ensure auctex
No, that does not work, because any customization below that comes from latex.el
(and probably other files in AUCTeX, e.g., context.el) will result in error
messages.
`(use-package latex' will load tex.el, but not the other way round.
Perhaps the right way to use use-package with AUCTeX is to have separate
stanzas like
(use-package tex
(use-package latex
(use-package contex
etc., but that is cumbersome.
All the best,
Greg
TeX-style-path
Hi, I'm having a problem with TeX-style-path that I don't understand.
In my config, I set the values for TeX-auto-global, TeX-auto-private,
TeX-auto-local, TeX-style-private, and TeX-style-local variables.
TeX-style-path is constructed from these.
But when I C-h v TeX-style-path, I get this result:
Value
("~/.emacs.d/auctex" "/home/greg/.emacs.d/elpa/auctex-12.3.1/style"
"/home/greg/.emacs.d/auctex/auto" "/home/greg/.emacs.d/auctex/style" "auto"
"style")
Original Value
("~/.cache/emacs/autoparse" "/home/greg/.emacs.d/elpa/auctex-12.3.1/style"
126 47 46 99 97 104 101 109 115 117 116 111 112 114 120 "~/.cache/emacs/auctex")
It seems that my modifications are treated as the original value but the actual
value is the defaults. Do I understand that correctly? Does something restore
the defaults after my init file is loaded? I don't understand.
I use use-package to load auctex, following the directions from
https://emacs.stackexchange.com/questions/34189/emacs-setup-for-latex-after-use-package-verse
So I have
(use-package latex
:ensure auctex
:mode ("\\.tex\\'" . LaTeX-mode)
[...]
:config
[...]
TeX-auto-global (concat user-cache-directory "autoparse")
[etc]
Is this the right way to do it? And why am I getting the default values?
Thanks for any help.
Greg
Re: Adding to TeX-clean-default-intermediate-suffixes
On Wed 1 Apr 2020 at 15:13 Arash Esbati wrote:
> > Ah, I see. So it should be
> >
> > (setq LaTeX-clean-intermediate-suffixes
> > (append LaTeX-clean-intermediate-suffixes
> > '("\\.dvi" "\\.ent" "\\.fmt" "\\.rel" "\\.rip" "\\.tags" "\\.vrb")))
>
> I'm not sure if this helps, but from your description and how many
> packages try to add things to a variable, I suggest you use something
> like this in your init file:
>
> --8<---cut here---start->8---
> (with-eval-after-load "latex"
> (let ((ext '("\\.dvi" "\\.ent" "\\.fmt"
> "\\.rel" "\\.rip" "\\.tags"
> "\\.vrb")))
> (dolist (elt ext)
> (add-to-list 'LaTeX-clean-intermediate-suffixes elt t
> --8<---cut here---end--->8---
>
> It makes sure that your extensions are added to
> `LaTeX-clean-intermediate-suffixes' once latex.el is loaded, no matter how it
> is loaded. Using only
>
> (setq LaTeX-clean-intermediate-suffixes
> (append LaTeX-clean-intermediate-suffixes
> '("\\.dvi" "\\.ent" "\\.fmt" "\\.rel" "\\.rip" "\\.tags" "\\.vrb")))
>
> might end up in an error if it comes too early where
> `LaTeX-clean-intermediate-suffixes' isn't defined yet.
Thanks -- my corrected setq seems to be working so far.
In your suggestion, `with-eval-after-load' is used. But I load AUCTeX with
use-package, and I thought `with-eval-after-load' is not needed when use-package
is used.
All the best,
Greg
Re: Adding to TeX-clean-default-intermediate-suffixes
On Wed 1 Apr 2020 at 02:58 Joost Kremers wrote:
> On Tue, Mar 31 2020, Greg Bognar wrote:
> > In my init.el, there are two more packages that add to the list:
> > auctex-latexmk and latex-extra. latex-extra uses add-to-list and
> > auctex-latexmk uses append.
>
> Well, at least that tells us where "Notes.bib" comes from. :-)
>
> > So what I'd like to do is to append `LaTeX-clean-intermediate-suffixes' with
> > some more suffixes. However, doing
> >
> > (setq LaTeX-clean-default-intermediate-suffixes
> > '(append LaTeX-clean-default-intermediate-suffixes
> > '("\\.dvi" "\\.ent" "\\.fmt" "\\.rel" "\\.rip"
> > "\\.tags" "\\.vrb")))
> >
> > does not work. (Even if I completely comment out auctex-latexmk and
> > latex-extra.)
> >
> > What is the proper way to append `LaTeX-clean-intermediate-suffixes',
> > preserving all the other additions to it?
>
> The proper way is to actually set `LaTeX-clean-intermediate-suffixes`. (Check
> your `setq` above *carefully*... ;-P )
Ah, I see. So it should be
(setq LaTeX-clean-intermediate-suffixes
(append LaTeX-clean-intermediate-suffixes
'("\\.dvi" "\\.ent" "\\.fmt" "\\.rel" "\\.rip" "\\.tags" "\\.vrb")))
Embarrassing. Thanks!
Re: Adding to TeX-clean-default-intermediate-suffixes
[See below]
---
On Mon 30 Mar 2020 at 16:48 Joost Kremers wrote:
> On Mon, Mar 30 2020, Greg Bognar wrote:
> >> You should probably customize
> >> `LaTeX-clean-intermediate-suffixes`.
> >> `TeX-clean-default-intermediate-suffixes`
> >> just provides the default value for `LaTeX-clean-intermediate-suffixes`,
> >> which is why it's not a defcustom. (I assume that setting it doesn't have
> >> any effect because its value is not checked when cleaning out files. The
> >> value of `LaTeX-clean-intermediate-suffixes` is used for that.
> >
> > Thanks. I checked `LaTeX-clean-intermediate-suffixes` and its original
> > value is
> >
> > ("\\.aux" "\\.bbl" "\\.bcf" "\\.blg" "\\.brf" "\\.dvi" "\\.ent"
> > "\\.fdb_latexmk" "\\.fls" "\\.fmt" "\\.fot" "\\.glo" "\\.gls"
> > "\\.synctex\\.gz" "\\.idx" "\\.ilg" "\\.ind" "\\.lof" "\\.log" "\\.lot"
> > "\\.nav" "\\.out" "\\.rel" "\\.rip" "\\.snm" "\\.tags" "\\.toc" "\\.url"
> > "\\.vrb" "\\.run\\.xml" "\\.acn" "\\.acr" "\\.alg" "\\.glg" "\\.ist")
> >
> > which is my list, appended with ("\\.acn" "\\.acr" "\\.alg" "\\.glg"
> > "\\.ist")
> > as it should be from latex.el at (defcustom
> > LaTeX-clean-intermediate-suffixes...
> > at line 6061.
> >
> > But the actual value is
> > ("Notes\\.bib" "\\.tdo" "\\.aux" "\\.bbl" "\\.blg" "\\.brf" "\\.fot"
> > "\\.glo" "\\.gls" "\\.idx" "\\.ilg" "\\.ind" "\\.lof" "\\.log" "\\.lot"
> > "\\.nav" "\\.out" "\\.snm" "\\.toc" "\\.url" "\\.synctex\\.gz" "\\.bcf"
> > "\\.run\\.xml" "\\.fls" "-blx\\.bib" "\\.acn" "\\.acr" "\\.alg" "\\.glg"
> > "\\.ist" "\\.fdb_latexmk" "\\.aux.bak" "\\.fls")
> >
> >
> > So it seems `LaTeX-clean-intermediate-suffixes` *does* pick up my setq for
> > `TeX-clean-default-intermediate-suffixes`, but then something overrides it.
> > I
> > never use any "Notes.bib" file, so I don't think it's something in my
> > config.
> > Do you have any suggestions what it might be?
>
> Have you checked your config? Perhaps you set it a long time ago and forgot
> about it? (Happens to me more often than I care to admit. ;-) Or perhaps
> you're
> using some Emacs starter kit or a config from somewhere else? Or perhaps a
> file-local or dir-local variable?
> My advice would be to remove the `setq` from your config, customize
> `LaTeX-clean-intermediate-suffixes` to the value you want it to have and see
> what happens.
I now understand better what happens, but I still haven't solved the problem.
First, the `TeX-clean-default-intermediate-suffixes' variable is defined in
tex.el (l.2184, AUCTeX 12.2.0). Then the `LaTeX-clean-intermediate-suffixes'
variable takes its value and appends it with more suffixes in latex.el (l.6061).
In my init.el, there are two more packages that add to the list: auctex-latexmk
and latex-extra. latex-extra uses add-to-list and auctex-latexmk uses append.
So what I'd like to do is to append `LaTeX-clean-intermediate-suffixes' with
some more suffixes. However, doing
(setq LaTeX-clean-default-intermediate-suffixes
'(append LaTeX-clean-default-intermediate-suffixes
'("\\.dvi" "\\.ent" "\\.fmt" "\\.rel" "\\.rip" "\\.tags"
"\\.vrb")))
does not work. (Even if I completely comment out auctex-latexmk and
latex-extra.)
What is the proper way to append `LaTeX-clean-intermediate-suffixes', preserving
all the other additions to it?
I use use-package, if that makes any difference. I put the setq in the :config
part after
(use-package latex
:ensure auctex
:mode ("\\.tex\\'" . LaTeX-mode)
...
Thanks!
Re: Adding to TeX-clean-default-intermediate-suffixes
> > In my config, I have
> >
> > (setq TeX-clean-default-intermediate-suffixes
> > '("\\.aux" "\\.bbl" "\\.bcf" "\\.blg" "\\.brf" "\\.dvi" "\\.ent"
> > "\\.fdb_latexmk" "\\.fls" "\\.fmt" "\\.fot" "\\.glo" "\\.gls"
> > "\\.synctex\\.gz" "\\.idx" "\\.ilg" "\\.ind" "\\.lof" "\\.log"
> > "\\.lot" "\\.nav" "\\.out" "\\.rel" "\\.rip" "\\.snm" "\\.tags"
> > "\\.toc" "\\.url" "\\.vrb" "\\.run\\.xml"))
> >
> > I added a number of extra extensions to the default value for files created
> > by RefTeX, Beamer, Synctex, etc. I want to clean up all these files once
> > I'm done with a document.
> >
> > However, this does not work. E.g., it leaves RefTeX's .rel files around.
> > Why is that? Is it because TeX-clean-default-intermediate-suffixes is
> > defined by a defvar in tex.el, rather than a defcustom? Shouldn't this be a
> > customizable option in the first place? If not, what is the proper way to
> > add the extra extensions?
>
> You should probably customize
> `LaTeX-clean-intermediate-suffixes`. `TeX-clean-default-intermediate-suffixes`
> just provides the default value for `LaTeX-clean-intermediate-suffixes`, which
> is why it's not a defcustom. (I assume that setting it doesn't have any effect
> because its value is not checked when cleaning out files. The value of
> `LaTeX-clean-intermediate-suffixes` is used for that.
Thanks. I checked `LaTeX-clean-intermediate-suffixes` and its original value is
("\\.aux" "\\.bbl" "\\.bcf" "\\.blg" "\\.brf" "\\.dvi" "\\.ent"
"\\.fdb_latexmk" "\\.fls" "\\.fmt" "\\.fot" "\\.glo" "\\.gls"
"\\.synctex\\.gz" "\\.idx" "\\.ilg" "\\.ind" "\\.lof" "\\.log" "\\.lot"
"\\.nav" "\\.out" "\\.rel" "\\.rip" "\\.snm" "\\.tags" "\\.toc" "\\.url"
"\\.vrb" "\\.run\\.xml" "\\.acn" "\\.acr" "\\.alg" "\\.glg" "\\.ist")
which is my list, appended with ("\\.acn" "\\.acr" "\\.alg" "\\.glg" "\\.ist")
as it should be from latex.el at (defcustom LaTeX-clean-intermediate-suffixes...
at line 6061.
But the actual value is
("Notes\\.bib" "\\.tdo" "\\.aux" "\\.bbl" "\\.blg" "\\.brf" "\\.fot"
"\\.glo" "\\.gls" "\\.idx" "\\.ilg" "\\.ind" "\\.lof" "\\.log" "\\.lot"
"\\.nav" "\\.out" "\\.snm" "\\.toc" "\\.url" "\\.synctex\\.gz" "\\.bcf"
"\\.run\\.xml" "\\.fls" "-blx\\.bib" "\\.acn" "\\.acr" "\\.alg" "\\.glg"
"\\.ist" "\\.fdb_latexmk" "\\.aux.bak" "\\.fls")
So it seems `LaTeX-clean-intermediate-suffixes` *does* pick up my setq for
`TeX-clean-default-intermediate-suffixes`, but then something overrides it. I
never use any "Notes.bib" file, so I don't think it's something in my config.
Do you have any suggestions what it might be?
Adding to TeX-clean-default-intermediate-suffixes
In my config, I have
(setq TeX-clean-default-intermediate-suffixes
'("\\.aux" "\\.bbl" "\\.bcf" "\\.blg" "\\.brf" "\\.dvi" "\\.ent"
"\\.fdb_latexmk" "\\.fls" "\\.fmt" "\\.fot" "\\.glo" "\\.gls"
"\\.synctex\\.gz" "\\.idx" "\\.ilg" "\\.ind" "\\.lof" "\\.log"
"\\.lot" "\\.nav" "\\.out" "\\.rel" "\\.rip" "\\.snm" "\\.tags"
"\\.toc" "\\.url" "\\.vrb" "\\.run\\.xml"))
I added a number of extra extensions to the default value for files created by
RefTeX, Beamer, Synctex, etc. I want to clean up all these files once I'm done
with a document.
However, this does not work. E.g., it leaves RefTeX's .rel files around. Why
is that? Is it because TeX-clean-default-intermediate-suffixes is defined by a
defvar in tex.el, rather than a defcustom? Shouldn't this be a customizable
option in the first place? If not, what is the proper way to add the extra
extensions?
Thanks!
Re: AUCTeX and undo-tree
> On Wed, Mar 04 2020, Greg Bognar wrote: > > I use the undo-tree package from GNU Elpa. Recently, the undo command > > (undo-tree-undo) stopped working when I edit .tex files with AUCTeX (in > > LaTeX-mode). As far as I can tell, it works as expected in all other modes. > > Emacs seems to hang and I have to hit C-g repeatedly to be able to edit > > again. The default M-x undo command still works. > > I'm not seeing any problem, undo-tree works just fine in AUCTeX. > > What versions of Emacs and AUCTeX are you using? What OS? I'm on Linux, Emacs > 26.3 and AUCTeX 12.2.0. I'm on Debian 10.3, Emacs 26.1, AUCTeX 12.2.0. Of course now I'm unable to reproduce the error. It seems to appear randomly. What I do remember is that it started after the latest update of undo-tree. I'm quite sure it has to do with my config, with the Emacs sandbox I don't see it at all. > > Since I have a lot of customizations, it's possible the cause is somewhere > > in my init file. But before I try to track it down, I wonder if anyone else > > experienced this problem and have some ideas. > > Check out Emacs sandbox: > > https://github.com/alphapapa/emacs-sandbox.sh > > It allows you to run a clean Emacs instance without your customisations. You > can then install AUCTeX and undo-tree into that instance (Melpa is > pre-configured) and test if the problem occurs. When you quit Emacs, > everything is cleaned up. Your config isn't touched at all, you can even start > the Emacs sandbox safely while your regular Emacs is running. > > This way you can find out if your config has anything to do with the issue > you're seeing. Emacs sandbox is great! Thanks for the pointer.
AUCTeX and undo-tree
I use the undo-tree package from GNU Elpa. Recently, the undo command (undo-tree-undo) stopped working when I edit .tex files with AUCTeX (in LaTeX-mode). As far as I can tell, it works as expected in all other modes. Emacs seems to hang and I have to hit C-g repeatedly to be able to edit again. The default M-x undo command still works. Since I have a lot of customizations, it's possible the cause is somewhere in my init file. But before I try to track it down, I wonder if anyone else experienced this problem and have some ideas. Thanks!
Re: [AUCTeX] Loading beamer.el style file (Was: font-locking problem)
Thanks, it works!
On Sat 16 Feb 2019 at 14:44 Mandar Mitra wrote:
> Greg Bognar wrote (Sat, Feb 16, 2019 at 01:49:09AM +0100):
> > I'd like to follow up on this. I have looked into the package
> > "beamerswitch",
> > which does what I was trying to do (generate slides, handouts, notes, etc.
> > from
> > one source file). However, it has the same problem with font-locking, due
> > to
> > beamer.el not being loaded. In this case, C-c C-n does not help either,
> > since
> > the documentclass is beamerswitch, not beamer.
> >
> > So, feature request: couldn't both \documentclass{beamerswitch} and
> > \usepackage{beamerarticle} load beamer.el? I can see no reason they
> > shouldn't.
> >
> > Alternatively, is there a user option I could set so that when I open a file
> > with \documentclass{beamerswitch} or \usepackage{beamerarticle}, beamer.el
> > is
> > loaded?
>
> This may not be the "proper" way to do things (I'm no expert), but it might
> work:
>
> 1. create a file called beamerswitch.el in the directory pointed to by your
> TeX-style-private variable;
>
> 2. in the file, put
>(TeX-add-style-hook
> "beamerswitch"
> (lambda ()
> (TeX-run-style-hooks "beamer")))
>
> 3. repeat for beamerarticle.
>
> HTH,
> mandar
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
[AUCTeX] Loading beamer.el style file (Was: font-locking problem)
I'd like to follow up on this. I have looked into the package "beamerswitch",
which does what I was trying to do (generate slides, handouts, notes, etc. from
one source file). However, it has the same problem with font-locking, due to
beamer.el not being loaded. In this case, C-c C-n does not help either, since
the documentclass is beamerswitch, not beamer.
So, feature request: couldn't both \documentclass{beamerswitch} and
\usepackage{beamerarticle} load beamer.el? I can see no reason they shouldn't.
Alternatively, is there a user option I could set so that when I open a file
with \documentclass{beamerswitch} or \usepackage{beamerarticle}, beamer.el is
loaded?
Thanks!
On Sun 10 Feb 2019 at 18:19 Greg Bognar wrote:
>
> > C-c # (bound to TeX-normal-mode (qv) by default) works for me. It's what I
> > do
> > after I've added new packages, changed the document class, or made similar
> > changes. Maybe you could give that a go?
>
> Yes, that works. Thanks!
>
> But now that I understand what the problem was, I'm wondering: shouldn't
> \usepackage{beamerarticle} trigger the loading of beamer.el? Then the problem
> wouldn't occur in the first place.
>
> Thanks again,
> Greg
>
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] font-locking problem
> C-c # (bound to TeX-normal-mode (qv) by default) works for me. It's what I do
> after I've added new packages, changed the document class, or made similar
> changes. Maybe you could give that a go?
Yes, that works. Thanks!
But now that I understand what the problem was, I'm wondering: shouldn't
\usepackage{beamerarticle} trigger the loading of beamer.el? Then the problem
wouldn't occur in the first place.
Thanks again,
Greg
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] font-locking problem
l AUCTeX explicitly to
re-scan the file and load the style files for document classes or packages it
finds? So when I open a file with \documentclass...{article} uncommented, and
subsequently uncomment \documentclass...{beamer}, then I can tell AUCTeX to load
beamer.el?
- Or is there a reason \usepackage{beamerarticle} doesn't cause beamer.el to be
loaded? It seems it should.
Finally, my preamble also has stuff like
\mode{ %
\usepackage{arevmath} %
...
and
\mode{%
\usepackage{fancyhdr} %
...
AUCTeX will load all the style files for the packages, regardless of the mode
they are used in, right? That seems to be the case.
Any advice on how to fix this?
Thanks for the pointer,
All the best,
Greg
> Date: Sat, 09 Feb 2019 10:32:45 +0100
> From: Tassilo Horn
> To: auctex@gnu.org
> Subject: Re: [AUCTeX] font-locking problem
> Message-ID: <8736oxxq6a@gnu.org>
> Content-Type: text/plain
>
> Greg Bognar writes:
>
> Hi Greg,
>
> > I have an odd font-locking problem in AUCTeX. When I work on Beamer
> > slides, sometimes the font-locking works as in the "good" version of
> > the screenshot attached.
>
> Thanks for the good description! In the "bad" version, the beamer.el
> style hasn't been loaded, or at least not the following snippet in it:
>
>;; Fontification
>(when (and (featurep 'font-latex)
> (eq TeX-install-font-lock 'font-latex-setup))
> (font-latex-add-keywords '(("title" "[{")
> ("subtitle" "[{")
> ("author" "[{")
> ("date" "[{")
> ("frametitle" "<[{")) 'slide-title)
>
> That would have told font-latex how to highlight \frametitle.
>
> The question is just, why it sometimes fails to load. In the bad case,
> maybe there's something in *Messages*? What's the value of
> `TeX-style-path' in the good and the bad case?
>
> Bye,
> Tassilo
>
> > Date: Sat, 09 Feb 2019 01:22:09 +0100
> > From: Greg Bognar
> > To: auctex@gnu.org
> > Subject: [AUCTeX] font-locking problem
> > Message-ID: <87tvhdak0e.wl-greg.bog...@startmail.com>
> > Content-Type: text/plain; charset="us-ascii"
> >
> > Hi,
> >
> > I have an odd font-locking problem in AUCTeX. When I work on Beamer slides,
> > sometimes the font-locking works as in the "good" version of the screenshot
> > attached. The faces are:
> >
> > Good version:
> > \begin (font-lock-keyword-face font-latex-sedate-face)
> > frame (font-lock-function-name-face)
> > \frametitle (font-lock-keyword-face font-latex-sedate-face)
> > < (font-latex-sedate-face)
> > presentation (font-lock-variable-name-face font-latex-sedate-face)
> > My Slide (font-latex-slide-title-face)
> >
> > Other times, font-locking works as in the "bad" version of the screenshot
> > attached. The faces are:
> >
> > Bad version:
> > \begin (font-lock-keyword-face font-latex-sedate-face)
> > frame (font-lock-function-name-face)
> > \frametitle (font-latex-sedate-face)
> > < (font-latex-sedate-face)
> > presentation (font-latex-sedate-face)
> > My Slide No face
> >
> > This seems completely random. This is the same file, same Emacs session,
> > same
> > customizations; sometimes the "good" version is turned on, sometimes the
> > "bad"
> > version. I can't tell what makes the difference (e.g., restarting Emacs
> > seems
> > to make no difference).
> >
> > How can I track down what the problem might be?
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
[AUCTeX] font-locking problem
Hi, I have an odd font-locking problem in AUCTeX. When I work on Beamer slides, sometimes the font-locking works as in the "good" version of the screenshot attached. The faces are: Good version: \begin (font-lock-keyword-face font-latex-sedate-face) frame (font-lock-function-name-face) \frametitle (font-lock-keyword-face font-latex-sedate-face) < (font-latex-sedate-face) presentation (font-lock-variable-name-face font-latex-sedate-face) My Slide (font-latex-slide-title-face) Other times, font-locking works as in the "bad" version of the screenshot attached. The faces are: Bad version: \begin (font-lock-keyword-face font-latex-sedate-face) frame (font-lock-function-name-face) \frametitle (font-latex-sedate-face) < (font-latex-sedate-face) presentation (font-latex-sedate-face) My Slide No face This seems completely random. This is the same file, same Emacs session, same customizations; sometimes the "good" version is turned on, sometimes the "bad" version. I can't tell what makes the difference (e.g., restarting Emacs seems to make no difference). How can I track down what the problem might be? ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] How to modify TeX-view-program-selection
Thanks for the suggestions. Replacing "zathura" with "Zathura" helps, but also removing the extra pair of parentheses around "((output-pdf "Zathura")): (add-hook 'LaTeX-mode-hook '(lambda () ;some other stuff (add-to-list 'TeX-view-program-selection '(output-pdf "Zathura")) )) > There's no need to do this in LaTeX-mode-hook, it should be enough to have > (add-to-list 'TeX-view-program-selection '((output-pdf "Zathura"))) (with-eval-after-load 'tex (add-to-list 'TeX-view-program-selection '((output-pdf "Zathura" for reasons David mentioned. > in your init file. Doing it in LaTeX-mode-hook means it's executed each > time you open a LaTeX file, which is harmless but unnecessary. > > Note, though, that Zathura is defined in TeX-view-program-list-builtin as > "Zathura" (note the capital Z), so that's what you need to put in > TeX-view-program-selection. (I suspect that is the cause of your troubles.) Yes. Thanks for pointing it out. > As for the entry for Evince in TeX-view-program-selection, I have no idea if > that conflicts, but if you need to get rid of that, you could do: > > (setcdr (assq 'output-pdf TeX-view-program-selection) "Zathura") This leads to an error: Wrong type argument: listp, "Zathura" The value of TeX-view-program-selection: (((output-dvi has-no-display-manager) "dvi2tty") ((output-dvi style-pstricks) "dvips and gv") (output-dvi "xdvi") (output-pdf . "Zathura") (output-html "xdg-open")) I guess the problem is the extra period. > instead of the add-to-list invocation above. But I suspect that AUCTeX will > simply use the first matching entry in TeX-view-program-selection, so the > entry for Evince shouldn't cause problems. OK, but now each time I C-c C-c, I get a prompt: View command: zathura file.pdf Is it possible to get rid of the prompt? Or should I just use C-c C-v instead? ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
[AUCTeX] Follow-up: How to modify TeX-view-program-selection
I've just realized that (setq TeX-view-program-selection '((output-pdf "zathura"))) doesn't work either. It now complains that Unknown "zathura" viewer. Check the `TeX-view-program-selection' variable So I'm obviously on the wrong track. (Until now, I have launched a PDF viewer manually, so I haven't run into this problem.) ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
[AUCTeX] How to modify TeX-view-program-selection
Hi, I suppose this question comes up often, but I couldn't find a solution. I wanted to try another PDF viewer for AUCTeX (zathura). Since it's already in TeX-view-program-list-builtin, I don't have to add it to TeX-view-program-list. So I thought I just have to modify TeX-view-program-selection. TeX-view-program-selection's original value is (((output-dvi has-no-display-manager) "dvi2tty") ((output-dvi style-pstricks) "dvips and gv") (output-dvi "xdvi") (output-pdf "Evince") (output-html "xdg-open")) If I do (setq TeX-view-program-selection '((output-pdf "zathura"))) then the value is ((output-pdf "zathura")) which deletes all the other items. I want to add to the list, not replace it entirely. So I tried (add-hook 'LaTeX-mode-hook '(lambda () (add-to-list 'TeX-view-program-selection '((output-pdf "zathura"))) )) And now the value is (((output-pdf "zathura")) ((output-dvi has-no-display-manager) "dvi2tty") ((output-dvi style-pstricks) "dvips and gv") (output-dvi "xdvi") (output-pdf "Evince") (output-html "xdg-open")) And when I try to use the view command, I get Cannot find "Evince" viewer. Select another one in `TeX-view-program-selection' I was under the impression that add-to-list is supposed to override the original value, but that does not seem to happen. I think I'm missing something obvious here. How can I replace (output-pdf "Evince") without deleting all the other items on the list as well? Thanks, Greg ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] auctex Digest, Vol 156, Issue 8
> Arash Esbati writes: > > I didn't test it, but could you please use two distinct names for your > > files, e.g. foo.tex and bar.bib, and try it again? > > Thanks, that does the trick! For posterity, the `.bib' file must not have the > same filename as _any_ other file in the directory, i.e., calling `bar.bib' > from `foo.tex' will not work if there is a `bar.tex' in the same directory. Is there any reason this might be so? I'm asking because I'm doing exactly what you say I shouldn't, and it works without any problems. Greg ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] TeX-clean in multifile document
Hi Mosè, Yes, I'm using \include. I understand that \input does not create extra .aux files, so there it's not an issue, but then I cannot use \includeonly. So I guess it's a trade off between two convenience features. Thanks for the clarification! Greg On Sat 10 Feb 2018 at 19:24 Mosè Giordano wrote: > Hi Greg, > > 2018-02-10 19:16 GMT+01:00 Greg Bognar : > > Hi, > > > > Say you are working on a multifile document with file1.tex, file2.tex, etc, > > and > > with the master file masterfile.tex. It's handy to clean up the generated > > files > > with TeX-clean. However, TeX-clean will only delete files which have the > > base > > name of the master file, i.e., masterfile.*. But TeX also generates .aux > > files > > for file1.tex, file2.tex, etc., and these are not deleted. Is there a way > > to > > have TeX-clean delete these files as well? Or is there any reason this > > would > > not be a good idea? > > > > (I tried putting "*\\.aux" in TeX-clean-default-intermediate-suffixes list > > of > > extensions, but it didn't work.) > > > > This is mostly a matter of convenience, but I'm curious if it's possible. > > I guess you're "\include"ing the files, rather than "\input"ting them, > right? I agree it would be a good idea to clean up the auxiliary > files for secondary files, but the way AUCTeX currently records the > names of the included files this isn't supereasy. They're listed in > `TeX-active-styles', but mixed together with classes and packages, so > it's difficult to extract just the names of the included files. > > Unless you have a real need to use "\include", with "\input" you don't > have multiple auxiliary files. > > Bye, > Mosè ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
[AUCTeX] TeX-clean in multifile document
Hi, Say you are working on a multifile document with file1.tex, file2.tex, etc, and with the master file masterfile.tex. It's handy to clean up the generated files with TeX-clean. However, TeX-clean will only delete files which have the base name of the master file, i.e., masterfile.*. But TeX also generates .aux files for file1.tex, file2.tex, etc., and these are not deleted. Is there a way to have TeX-clean delete these files as well? Or is there any reason this would not be a good idea? (I tried putting "*\\.aux" in TeX-clean-default-intermediate-suffixes list of extensions, but it didn't work.) This is mostly a matter of convenience, but I'm curious if it's possible. All the best, Greg ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
[AUCTeX] Hi-lock and AUCTeX
Hi, I can't get Hi Lock mode to work with AUCTeX. https://www.gnu.org/software/emacs/manual/html_node/emacs/Highlight-Interactively.html It works fine with other major modes, but does nothing in files in LaTeX-mode. Does anyone know why this is? All the best, Greg ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] bib-cite
On 16/01/14 23:35, Mosè Giordano wrote: Hi Greg, 2014/1/16 Greg Bognar : Hi, AUCTeX (11.87.2012-12-04) fails to load properly on GNU Emacs 24.3.1 when bib-cite is turned on. The error message is: File mode specification error: (void-function make-local-hook) The bib-cite-minor-mode function calls make-local-hook on line 766 of bib-cite.el. As far as I know, this function was removed from Emacs 24. this has been already fixed in the development version of AUCTeX last September, with this commit: http://git.savannah.gnu.org/cgit/auctex.git/commit/bib-cite.el?id=9e0fae3919ba0fcd1ed2923f14574780db42174a Oh, OK. It's just not in the ELPA version yet. Best, Greg ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
[AUCTeX] bib-cite
Hi, AUCTeX (11.87.2012-12-04) fails to load properly on GNU Emacs 24.3.1 when bib-cite is turned on. The error message is: File mode specification error: (void-function make-local-hook) The bib-cite-minor-mode function calls make-local-hook on line 766 of bib-cite.el. As far as I know, this function was removed from Emacs 24. Cheers, Greg ___ auctex mailing list auctex@gnu.org https://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] Re: help write a function?
On Thu, 27 Jul 2006, Ralf Angeli wrote: > * Greg BOGNAR (2006-07-27) writes: > > >> > Like `C-c ?' (aka `TeX-doc') in AUCTeX? > >> > >> Wow, this is fabulous! I used to rely on texdoctk, but now with TeX-doc, > >> we can stay in Emacs, and not be distracted by having to launch a separate > >> application -- not to berate texdoctk in any way whatsoever. > > > > I've just learnt about texdoc from this exchange, and it looks great, > > but can you point to the information that explains how it can be used > > from under Emacs? > > I don't understand the question given that the past discussion is > related to an interface for (but not limited to) texdoc. I meant I got the impression that there is a TeX-doc command in AUCTeX. I have no such command in my setup, though I do have a texdoc command-line utility. Greg ___ auctex mailing list auctex@gnu.org http://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] Re: help write a function?
> > Like `C-c ?' (aka `TeX-doc') in AUCTeX? > > Wow, this is fabulous! I used to rely on texdoctk, but now with TeX-doc, > we can stay in Emacs, and not be distracted by having to launch a separate > application -- not to berate texdoctk in any way whatsoever. I've just learnt about texdoc from this exchange, and it looks great, but can you point to the information that explains how it can be used from under Emacs? Thanks, Greg ___ auctex mailing list auctex@gnu.org http://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] Formatting and syntax highlighting
> 2. Is there any way to enhance syntax highlighting in math mode? I'd > like to have normal text and greek character macros in one color and > other macros (like \sqrt, etc.) as well as maybe symbols (as "+") in > another color because I think that would make it easier to read. You could try using Emacs's hi-lock package which lets you define and highlight arbitrary regular expressions. Greg ___ auctex mailing list auctex@gnu.org http://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] BIBINPUTS
On Sun, 29 Jan 2006, Ralf Angeli wrote: > * Greg BOGNAR (2006-01-28) writes: > > > On Sat, 28 Jan 2006, Ralf Angeli wrote: > > > >> So how do you set it? > > > > In my .bashrc: > > > > BIBINPUTS=.:$HOME/Documents/bibliographies//: > > > > As I mentioned before, a latex job run from the terminal finds the > > databases, only Emacs doesn't. > > Does it work if you export the variable? No, it doesn't. As far as I understand from the bash manpage, variables defined in .bashrc do not have to be exported, in any case. Wouldn't the simple solution be to introduce a variable for the bibliography databases within AUCTeX? I think there are such variables in RefTeX and Bib-cite. Greg ___ auctex mailing list auctex@gnu.org http://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] BIBINPUTS
On Sat, 28 Jan 2006, Ralf Angeli wrote: > * Greg BOGNAR (2006-01-28) writes: > > >> * Greg BOGNAR (2006-01-26) writes: > > > >>> I have bibligraphy databases in a dedicated directory. I set > >>> BIBINPUTS for that directory. > > > >> How do you set BIBINPUTS? In my case I have > >> BIBINPUTS = .;$TEXMF/bibtex/bib// > >> in /etc/texmf/texmf.cnf. > > > > Same here. But I want to set it to ~/Documents/bibliographies or > > something like that, not ~/texmf/bibtex/bib. My bibliography > > databases should be kept together with the rest of my documents. > > So how do you set it? In my .bashrc: BIBINPUTS=.:$HOME/Documents/bibliographies//: As I mentioned before, a latex job run from the terminal finds the databases, only Emacs doesn't. > > Meanwhile, I got a solution from Fernando Tusell, I hope he does not > > mind that I copy parts of his message here: > > > >> I had a problem similar to yours: starting a session under bash, I > >> could find files pointed to by BIBINPUTS, but not otherwise. > > > >> It turned out that when I started Emacs from a graphical session in > >> Gnome, the file .bashrc (where the environment variable BIBINPUTS is > >> set) was not read. The simple fix in my case was to set BIBINPUTS in > >> file .gnomerc (and later I found that making a link from .gnomerc to > >> .bashrc also works, and I only have to change and maintain .bashrc). > > > > I use Fvwm, and the solution was the same: I just set BIBINPUTS again > > in my .fvwm/config. Now it all works. But I doubt it has to do with > > the graphical session; it does not work when I run Emacs without X. > > It seems that Emacs does not read .bashrc at all. > > ,[ bash(1) ] > | When bash is invoked as an interactive login shell, or as a non-inter- > | active shell with the --login option, it first reads and executes com- > | mands from the file /etc/profile, if that file exists. After reading > | that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, > | in that order, and reads and executes commands from the first one that > | exists and is readable. The --noprofile option may be used when the > | shell is started to inhibit this behavior. > ` > > Perhaps you need to source .bashrc in .bash_profile. Of course it is: if [ -f ~/.bashrc ]; then . ~/.bashrc fi Cheers, Greg ___ auctex mailing list auctex@gnu.org http://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] BIBINPUTS
> * Greg BOGNAR (2006-01-26) writes: >> I have bibligraphy databases in a dedicated directory. I set >> BIBINPUTS for that directory. > How do you set BIBINPUTS? In my case I have > BIBINPUTS = .;$TEXMF/bibtex/bib// > in /etc/texmf/texmf.cnf. Same here. But I want to set it to ~/Documents/bibliographies or something like that, not ~/texmf/bibtex/bib. My bibliography databases should be kept together with the rest of my documents. >> When I run BibTeX in bash, it sees the databases in that directory. >> When I use Emacs, it does not find those files. Running BibTeX >> from Emacs (+ AUCTeX) gives an error message like "I couldn't open >> database file bibliography.bib ---line 5 of file mydoc.aux" > How do you run BibTeX from Emacs? > As an example I created a file foo.bib in > /home/angeli/texmf/bibtex/bib and a LaTeX file with the contents [...] > somewhere else. After running LaTeX with `C-c C-c RET' and BibTeX > with `C-c C-c BibTeX RET' I get the following output in the output > buffer for the document (accessible with `C-c C-l'): [...] The very same steps here, but with error messages. Meanwhile, I got a solution from Fernando Tusell, I hope he does not mind that I copy parts of his message here: > I had a problem similar to yours: starting a session under bash, I > could find files pointed to by BIBINPUTS, but not otherwise. > It turned out that when I started Emacs from a graphical session in > Gnome, the file .bashrc (where the environment variable BIBINPUTS is > set) was not read. The simple fix in my case was to set BIBINPUTS in > file .gnomerc (and later I found that making a link from .gnomerc to > .bashrc also works, and I only have to change and maintain .bashrc). I use Fvwm, and the solution was the same: I just set BIBINPUTS again in my .fvwm/config. Now it all works. But I doubt it has to do with the graphical session; it does not work when I run Emacs without X. It seems that Emacs does not read .bashrc at all. Thanks, Greg ___ auctex mailing list auctex@gnu.org http://lists.gnu.org/mailman/listinfo/auctex
Re: [AUCTeX] BIBINPUTS
I have bibligraphy databases in a dedicated directory. I set BIBINPUTS for that directory. When I run BibTeX in bash, it sees the databases in that directory. When I use Emacs, it does not find those files. Running BibTeX from Emacs (+ AUCTeX) gives an error message like "I couldn't open database file bibliography.bib ---line 5 of file mydoc.aux" Actually, when I run emacs -q, it does see the bibliography databases. It is only when I run emacs without -q that it does not. But it cannot be something in my init files, since the same error happens when I run emacs with an empty .emacs or .emacs.d/init.el file, or even when no startup file or directory exists at all. emacs -q does not run default.el either, but I don't have a default.el file. I use GNU Emacs 22.0.50.1, GTK+ on Ubuntu Breezy, with AUCTeX 11.55. AUCTeX is enabled by default for the whole site. Thanks, Greg On Wed, 25 Jan 2006, Ralf Angeli wrote: > Please use the new mailing list address. > > * Greg BOGNAR (2006-01-24) writes: > > > this is probably a very simple question, but whatever I do, I cannot > > teach AucTeX the location of my bibliography files. I have BIBINPUTS > > set, but AucTeX does not seem to see it. I could not find any > > information about this in the AucTeX manual. > > Could you please explain what you want to achieve, what actions you > have taken in order to achieve your goal, and in what way AUCTeX > failed? > > ___ auctex mailing list auctex@gnu.org http://lists.gnu.org/mailman/listinfo/auctex
[AUCTeX] BIBINPUTS
Hi, this is probably a very simple question, but whatever I do, I cannot teach AucTeX the location of my bibliography files. I have BIBINPUTS set, but AucTeX does not seem to see it. I could not find any information about this in the AucTeX manual. I use AucTeX 11.55. Thanks in advance, Greg ___ auctex mailing list auctex@gnu.org http://lists.gnu.org/mailman/listinfo/auctex
