emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Bruno BEAUFILS <bruno@boulgour.com>
Cc: 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 13:30:37 +0000	[thread overview]
Message-ID: <873574berm.fsf@localhost> (raw)
In-Reply-To: <20230217131845.ein4q6ig2gcytjtc@settat>

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?

>> variable, or, like John Kitchin often does, put the following src block
>> on the top of your file and use it for exporting:
>> 
>> #+begin_src emacs-lisp :exports none
>> (let (<your overrides>) (org-latex-export-to-pdf))
>> #+end_src
>
> I want to be able to use my file interactively as well as in batch
> mode, I thus think that this proposition is not really a good solution
> even if I find it elegant.

You can do it in batch as well. See `org-sbe'.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2023-02-17 13:30 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 [this message]
2023-02-17 14:39           ` Jean Louis
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=873574berm.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=bruno@boulgour.com \
    --cc=emacs-orgmode@gnu.org \
    /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).