emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Hanno Perrey <hanno@hoowl.se>
To: emacs-orgmode@gnu.org, Bruno BEAUFILS <bruno@boulgour.com>,
	"Thomas S. Dye" <tsd@tsdye.online>
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 06:54:16 +0100	[thread overview]
Message-ID: <3EE20F8E-6FE3-4CE5-93C4-3D8F35B348CD@hoowl.se> (raw)
In-Reply-To: <20230215203855.fltqggfs34rh2tkl@settat>

Bruno BEAUFILS <bruno@boulgour.com> skrev: (15 februari 2023 21:38:55 CET)
>On Wed, Feb 15, 2023 at 09:34:21AM -1000, Thomas S. Dye wrote:
>> I often use the .tex file to track down compilation issues.  I don't want
>> Org to delete it.
>
>I get your point. In that case the file must not be removed when the
>compilation failed.
>
>In all other (more numerous) cases (when everything went well) what is
>the point to have this file in addition to the source and the output?
>
>-- 
>Bruno BEAUFILS

I see the export to PDF as a shortcut only and appreciate having the .tex file besides it. As the TeX file is the most reliable way to regenerate the exact PDF again later again (even on other peoples' machines without Emacs installed) I like to keep it in many cases "for the record".

I would personally opt for keeping the current default, that is keeping the TeX file.


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

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=3EE20F8E-6FE3-4CE5-93C4-3D8F35B348CD@hoowl.se \
    --to=hanno@hoowl.se \
    --cc=bruno@boulgour.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.online \
    /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).