em...@vergauwen.me writes:
> 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 di
First time to hear that.
I wasn’t aware of it 8-0.
Will need to recheck my projects and settings to see what I was accidentally
doing right… in the sense that it was working as intended…
Thx/PA
PS: once again I’ll go to sleep and will have learnt something new (as the
Spanish proverb goes)
E
> >>> 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 brea
>Message-ID: <87fsjfn7jw.fsf@localhost>
>emacs--- via "General discussions about Org-mode."
> writes:
>
>>> 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 sec
Daniel Fleischer writes:
> Ihor Radchenko [2022-07-05 Tue 19:05] wrote:
>
>> 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).
>> Thi
Ihor Radchenko [2022-07-05 Tue 19:05] wrote:
> 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 be
emacs--- via "General discussions about Org-mode."
writes:
>> 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 i
Hi Daniel,
>> in the attachment you find a proposed patch to support including external
>> files
>> when exporting a latex source block. Currently this was only possible by
>> using a
>> :header argument. The problem with this approach is that, files needed to be
>> included with their absolute
emacs--- via "General discussions about Org-mode." [2022-07-04 Mon 21:15] wrote:
> in the attachment you find a proposed patch to support including external
> files
> when exporting a latex source block. Currently this was only possible by
> using a
> :header argument. The problem with this appr
Dear list,
in the attachment you find a proposed patch to support including external files
when exporting a latex source block. Currently this was only possible by using a
:header argument. The problem with this approach is that, files needed to be
included with their absolute path.
My propose
10 matches
Mail list logo