Typo, sorry list! Please ignore. Works as expected.
On Tue, Mar 30, 2021 at 7:02 PM Thangalin wrote:
> Given test.tex:
>
> % SOF
> \starttext
> Guten abend
> \stoptext
> % EOF
>
> Run: context --puregeall --result=out.pdf test.tex
>
> Expected: All .tuc and .log files are deleted.
>
> Actual: ou
Given test.tex:
% SOF
\starttext
Guten abend
\stoptext
% EOF
Run: context --puregeall --result=out.pdf test.tex
Expected: All .tuc and .log files are deleted.
Actual: out.log and out.tuc are not deleted.
Context version: 2021.03.27 19:09
Cheers!
___
>From https://wiki.contextgarden.net/Run_scripts
context --jit prd_${PRD} --result=_pdf/$RESULT --mode=$MOD
Does this mean the example is incorrect? Or did it once work and the
behaviour has since changed? Or is it that relative directories are fine
but absolute paths won't work?
Let me know and
schrieb am Di., 30. März 2021, 09:45:
> Hi,
>
> I have file main.tex that loads various subfiles that are placed in a
> subdir :
>
>
>
> \starttext
>
> \input subdir/chapter1
>
> \stoptext
>
>
>
> Chapter1.tex itself loads some other files that are also placed in the
> subdir directory :
>
> \sta
> Am 30.03.2021 um 10:23 schrieb
> :
>> BTW I’d strongly suggest to use the project structure (environment,
>> products, components) in such cases, but that doesn’t change this.
>
> I use environments, but in that particular case there's no need for products
> and components. (OTOH, with compo
> -Ursprüngliche Nachricht-
> Von: ntg-context Im Auftrag von Henning
> Hraban Ramm
> Gesendet: Dienstag, 30. März 2021 10:14
> An: mailing list for ConTeXt users
> Betreff: Re: [NTG-context] Nested structure of files loaded by input
>
>
>
> > Am 30.03.2021 um 09:43 schrieb denis.ma...
> Am 30.03.2021 um 09:43 schrieb denis.ma...@ub.unibe.ch:
> What am I missing ? Does \input resolve filenames according to the CWD, not
> to the location itself is located ?
Nothing. You need to decide from where you want to run your files.
BTW I’d strongly suggest to use the project structure
Ok, I can make it work with \doiffileexistselse
But is there a more elegant way ?
Von: ntg-context Im Auftrag von
denis.ma...@ub.unibe.ch
Gesendet: Dienstag, 30. März 2021 09:44
An: ntg-context@ntg.nl
Betreff: [NTG-context] Nested structure of files loaded by input
Hi,
I have file main.tex t
On 3/30/2021 9:13 AM, Henning Hraban Ramm wrote:
Am 30.03.2021 um 07:05 schrieb Thangalin :
How do you set the target output path and file name? Consider:
context --result=/tmp/subdir/test.pdf $HOME/test.tex
Expected: PDF file is created in /tmp/subdir directory.
Actual: PDF file is created
Hi,
I have file main.tex that loads various subfiles that are placed in a subdir :
\starttext
\input subdir/chapter1
\stoptext
Chapter1.tex itself loads some other files that are also placed in the subdir
directory :
\starttext
\input subfile1
\stoptext
Subfile1 :
\starttext
Asdf
\stopttext
No
IIRC, there’s currently no support for this.
--result= can be used to rename the output file, but it can not be used to
create the file in a specific directory, nor to move it there.
Such a feature would be quite useful though, I think.
Maybe two options?
--result=foo.pdf => rename output to foo.
> Am 30.03.2021 um 07:05 schrieb Thangalin :
>
> How do you set the target output path and file name? Consider:
> context --result=/tmp/subdir/test.pdf $HOME/test.tex
>
> Expected: PDF file is created in /tmp/subdir directory.
>
> Actual: PDF file is created in $HOME directory.
That’s known b
12 matches
Mail list logo
