From: Jean Louis <bugs@gnu.support>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Bruno BEAUFILS <bruno@boulgour.com>, emacs-orgmode@gnu.org
Subject: Re: Bug: org-latex-export-to-pdf does not remove .tex file [9.4 (9.4-elpa @ /home/bruno/.emacs.d/elpa/org-9.4/)]
Date: Fri, 17 Feb 2023 17:39:30 +0300 [thread overview]
Message-ID: <Y++Roiokk0lNhM0C@protected.localdomain> (raw)
In-Reply-To: <873574berm.fsf@localhost>
* Ihor Radchenko <yantar92@posteo.net> [2023-02-17 16:32]:
> Bruno BEAUFILS <bruno@boulgour.com> writes:
>
> > On Fri, Feb 17, 2023 at 10:55:34AM +0000, Ihor Radchenko wrote:
> >> > How so?
> >>
> >> latexmk -interaction=nonstopmode
> >
> > Still do not get the problem. I though that the exit code of the
> > underlying process was used but after having try to understand some of
> > the ox-latel.el I discover that it seems to be done another way
> > (analysing the output if I am right).
>
> Even if we used exit code, what would it achieve?
- user wants PDF file
- with exit code other but zero there will be no PDF file
- display error or move user straight to LaTeX file to try it out
manually or find what is wrong.
Personally I use exit code from LaTeX processing.
- I like to be careful with existing PDF files, as sometimes PDF file
is exported in different way, and maybe I am making mistake. So I
like to be cautious about it.
- Here below `latex-function' must return zero and `pdf-file' must
exist for system to update it's Hyperlink correctly, and to launch
Evince PDF viewer.
- But if error status is not zero, I want to find myself in LaTeX file
straight, then I can try C-c C-a to understand why it did not work.
(defun hyperscope-latex-to-pdf (id)
(let* ((default-directory (hyperscope-expand-directory-for-id id))
(latex-file (hyperscope-hyperdocument-file-name-full id "tex"))
(text (hyperscope-text id))
(pdf-file (hyperscope-hyperdocument-file-name-full id "pdf"))
(latex-function (lambda () (call-process "pdflatex" nil "*pdflatex*" nil latex-file))))
(string-to-file-force text latex-file)
(when (and (file-exists-p pdf-file)
(y-or-n-p "Delete existing PDF? "))
(delete-file pdf-file))
(cond ((and (zerop (funcall latex-function))
(file-exists-p pdf-file))
(rcd-db-update-entry "hyobjects" "hyobjects_link" id pdf-file hs-db)
(hyperscope-evince pdf-file))
(t (rcd-warning-message "Could not create PDF")
(find-file latex-file)))))
If I would just assume that `latex' command "just worked", that means
I am blindly continuing with some other functions thereafter, but that
would mean I am creating some errors.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-02-17 15:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 18:49 Bug: org-latex-export-to-pdf does not remove .tex file [9.4 (9.4-elpa @ /home/bruno/.emacs.d/elpa/org-9.4/)] Bruno BEAUFILS
2023-02-15 19:34 ` Thomas S. Dye
2023-02-15 20:38 ` Bruno BEAUFILS
2023-02-15 20:52 ` Alain.Cochard
2023-02-16 10:03 ` Bruno BEAUFILS
2023-02-16 10:30 ` Alain.Cochard
2023-02-16 5:54 ` Hanno Perrey
2023-02-16 10:15 ` Bruno BEAUFILS
2023-02-16 12:20 ` Hanno
2023-02-16 14:24 ` Bruno BEAUFILS
2023-02-16 18:47 ` Hanno Perrey
2023-02-16 19:58 ` Bruno BEAUFILS
2023-02-15 20:37 ` Ihor Radchenko
2023-02-16 10:22 ` Bruno BEAUFILS
2023-02-17 10:55 ` Ihor Radchenko
2023-02-17 13:18 ` Bruno BEAUFILS
2023-02-17 13:30 ` Ihor Radchenko
2023-02-17 14:39 ` Jean Louis [this message]
2023-02-17 18:10 ` Ihor Radchenko
2023-02-17 20:36 ` Bruno BEAUFILS
2023-02-18 10:52 ` [FR] ox-latex: Display exit status of LaTeX compilation command (was: Bug: org-latex-export-to-pdf does not remove .tex file [9.4 (9.4-elpa @ /home/bruno/.emacs.d/elpa/org-9.4/)]) Ihor Radchenko
2023-02-16 21:38 ` Bug: org-latex-export-to-pdf does not remove .tex file [9.4 (9.4-elpa @ /home/bruno/.emacs.d/elpa/org-9.4/)] Jean Louis
2023-02-16 20:51 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y++Roiokk0lNhM0C@protected.localdomain \
--to=bugs@gnu.support \
--cc=bruno@boulgour.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).