emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
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: Thu, 16 Feb 2023 23:51:49 +0300	[thread overview]
Message-ID: <Y+6XZfpnYG2TnR45@protected.localdomain> (raw)
In-Reply-To: <20230215184951.edu6n6k57lmfnqxz@settat>

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

* Bruno BEAUFILS <bruno@boulgour.com> [2023-02-15 21:52]:
> When using the org-latex-export-to-pdf on any foo.org file I get the
> foo.pdf file produced the right way but I also get the foo.tex file.
> 
> I think that the whole point of exporting to pdf is only to get the pdf
> file, avoiding the need to keep the latex one.
> 
> I guess that one of org-latex-compile or org-latex-export-to-pdf
> function should remove the source LaTeX file if the compile went well.

Good idea!

That will avoid clutter.

I can see that problem solved with simple function. One can use
different and temporary directory for that file, generate PDF, and
once there is no error message by `latex' command, and PDF is there,
that PDF can be moved to original directory.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2023-02-16 21:39 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
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 [this message]

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+6XZfpnYG2TnR45@protected.localdomain \
    --to=bugs@gnu.support \
    --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).