branch: externals/auctex-cont-latexmk
commit 1ffdaaf72231e1694d3e3fe6fc9fb79c4160d1df
Author: Paul Nelson <ultr...@gmail.com>
Commit: Paul Nelson <ultr...@gmail.com>
Add some clarifications and remarks to the readme
* README.org (Configuration):
---
README.org | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/README.org b/README.org
index 0c49a6b33e..ffa0f6d9b0 100644
--- a/README.org
+++ b/README.org
@@ -17,7 +17,7 @@ Replace the keybinding with whatever you prefer (or delete it
and just run the c
The command =tex-continuous-toggle= behaves the way that I prefer -- it
enables both =tex-continuous-mode= and =flymake-mode=, restricting the backends
for the latter to those coming from the former. Depending upon your
preferences, you may wish to write your own "wrapper" for =tex-continuous-mode=
akin to =tex-continuous-toggle=.
-The way the Flymake backend works, it will update only when the latexmk
process reaches a "watching for changes" state and the buffer is unmodified.
The workflow is thus to save the file, wait a few seconds for the compilation
to complete, and then to use Flymake to navigate the errors. I configure
Flymake to use =M-n= and =M-p= for navigation, and also use =(setq
flymake-show-diagnostics-at-end-of-line t)=, which displays the error/warning
messages in the buffer itself rather than jus [...]
+The way the Flymake backend works, it will update only when the latexmk
process reaches a "watching for changes" state and the buffer is unmodified.
The workflow is thus to save the file, wait a few seconds for the compilation
to complete, and then to use Flymake to navigate the errors. I configure
Flymake to use =M-n= and =M-p= for navigation, and also use =(setq
flymake-show-diagnostics-at-end-of-line t)= (available in Flymake 1.3.6, part
of Emacs 30+), which displays the error/warni [...]
#+begin_src elisp
(use-package flymake
@@ -29,6 +29,10 @@ The way the Flymake backend works, it will update only when
the latexmk process
("M-p" . flymake-goto-prev-error)))
#+end_src
+I also bind =flymake-show-diagnostics-buffer=, which gives an overview of all
errors. You can find my current setup in
[[https://github.com/ultronozm/emacsd/blob/main/init-main.el][my config]].
+
+Let me remark that TeX compilers are not so good at locating errors involving
braces. For this, the Emacs commands =check-parens=, =tex-validate-buffer= and
=tex-validate-region= are indispensable.
+
That's all. I prefer this workflow to the alternative in which one compiles
the document manually via =TeX-command-master= (=C-c C-c=) and navigates the
warning/error messages using =next-error= (=M-n=) and =previous-error= (=M-p=).
It also gives a handy way to keep the .aux files up-to-date; I take advantage
of this feature in the packages
[[https://github.com/ultronozm/czm-preview.el][czm-preview.el]] and
[[https://github.com/ultronozm/czm-tex-fold.el][czm-tex-fold.el]] to annotate t
[...]
* Customization
