From: emacs--- via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>, yantar92@gmail.com
Subject: Re: Re: [PATCH] ob-latex: Added support for including files with a relative path
Date: Wed, 6 Jul 2022 09:49:00 +0200 (CEST) [thread overview]
Message-ID: <N6HTxLN--3-2@vergauwen.me> (raw)
In-Reply-To: <CAO48Bk-dtE-8gP9MP0Am-vnw=6GiJx8DJekXFu6PPF+8izxGZg@mail.gmail.com-N6HJruU----2>
[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]
> >>> Hi, adding an "input" type of header is one option. What about adding a
> >>> call to resolve relative file names instead, thus solving maybe other
> >>> needs in addition?
> >>>
> >> That was my second approach. I was concerned that forcing all imports with
> >> an absolute path could break existing exports? Correct me if I'm wrong.
> >> Using the :header syntax external files can be loaded in via the old way,
> >> whereas using :inputs all relative paths are resolved.
> >> The downside of course is that we clutter the export settings with a new
> >> parameter.
> >
> >Rather than changing paths to absolute, we can simply play with the
> >working directly for latex process and set it to the directory of the
> >.org file (unless :dir argument is passed to the latex source block).
> >This is probably the most expected behavior.
> >
> >Best,
> >Ihor
>
> Just my .01 cents...
>
> For Latex stuff I'm using just
>
> #+HEADER: \input{preamble}
>
> and have my preamble.tex in the working directory. (For Beamer stuff it goes in a LATEX_HEADER).
>
> Changing that to
>
> #+HEADER :inputs '("preamble")
>
> well, would be a matter of taste.
>
Ox-beamer (ox-latex) executes all latex commands at the current directory of
your org file, whereas ob-latex uses a temporary file to do its thing.
(with-temp-file FILE &rest BODY)
I think this is mostly done to prent metafiles from cluttering your current
directory.
Different export types, or different user included packages, generate different
metafiles. This makes an automated cleanup process afterwards a bit more
complicated I think, if not impossible.
The temporary file makes it hard to add files to the working directory.
[-- Attachment #2: Type: text/html, Size: 2971 bytes --]
next prev parent reply other threads:[~2022-07-06 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 6:53 Re: [PATCH] ob-latex: Added support for including files with a relative path Pedro Andres Aranda Gutierrez
[not found] ` <CAO48Bk-dtE-8gP9MP0Am-vnw=6GiJx8DJekXFu6PPF+8izxGZg@mail.gmail.com-N6HJruU----2>
2022-07-06 7:49 ` emacs--- via General discussions about Org-mode. [this message]
2022-07-06 10:18 ` Pedro Andres Aranda Gutierrez
2022-07-07 10:52 ` Ihor Radchenko
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=N6HTxLN--3-2@vergauwen.me \
--to=emacs-orgmode@gnu.org \
--cc=emacs@vergauwen.me \
--cc=paaguti@gmail.com \
--cc=yantar92@gmail.com \
/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).