From: Alain.Cochard@unistra.fr
To: Bruno BEAUFILS <bruno@boulgour.com>
Cc: Alain.Cochard@unistra.fr, "Thomas S. Dye" <tsd@tsdye.online>,
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 11:30:39 +0100 [thread overview]
Message-ID: <25582.1487.277988.593767@gargle.gargle.HOWL> (raw)
In-Reply-To: <20230216100340.22rmgol4m74wy7pc@settat>
Bruno BEAUFILS writes on Thu 16 Feb 2023 11:03:
> OK but you still can do this by just export the file to LaTeX
> (buffer or file) when needed.
In general, I want to see the final result, if only to check that it
is correct latex (as far as I can see, any crap is happily transformed
into a .tex by 'C-c C-e l l'). So in practice, if I understand
correctly what you say, once the appropriate result (pdf) is obtained,
I would have to use an extra command (C-c C-e l l or C-c C-e l l) to
generate the .tex.
But I can understand your point, especially if you seldom use the
.tex, and I hope the developers can create a user option, as Ihor
proposed. I think most users will prefer the current situation to be
the default, though...
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 110] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | [ slot available for rent ]
next prev parent reply other threads:[~2023-02-16 10:31 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 [this message]
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
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=25582.1487.277988.593767@gargle.gargle.HOWL \
--to=alain.cochard@unistra.fr \
--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).