ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: A A via ntg-context <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Fwd: command line arguments to specify output directory
Date: Wed, 30 Mar 2022 18:45:14 -0400 (EDT)	[thread overview]
Message-ID: <nycvar.YAK.7.78.908.2203301843210.244301@nqv-guvaxcnq> (raw)
In-Reply-To: <CAMwawgPWhRNeQ5mfmn_exixP+kt3mto90f0ceO9y9pharod4PA@mail.gmail.com>

On Wed, 30 Mar 2022, A A via ntg-context wrote:
> On Wed, 30 Mar 2022 at 18:39, Wolfgang Schuster <
> wolfgang.schuster.lists@gmail.com> wrote:
> 
> > A A via ntg-context schrieb am 30.03.2022 um 18:24:
> > > Dear All,
> > >
> > > I would like to ask whether there exists a command line option to the
> > > context executable which would allow me to specify the directory in
> > > which I would like my output to be dumped.
> > >
> > > I have noticed that if I call the executable outside the directory in
> > > which the .tex file resides, my supporting files (and resulting pdf)
> > > are dumped outside the directory in which the .tex file is located.
> >
> > context --runpath=... filename
> 
>    - I tried the following *context --runpath=test test/test.tex * but it
>    still dumps all the output (.log, .pdf and .tuc) into my current directory.
>    I would like for it to get dumped inside the *test *directory...

mtxrun --path=test --script context test.tex

(note that filename has to be relative to the test/ directory not CWD)

Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-03-30 22:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 16:24 A A via ntg-context
2022-03-30 16:39 ` Wolfgang Schuster via ntg-context
     [not found]   ` <CAMwawgOWAQ+rDtf1sugYAccYWXkKMHG-uFLPh-p+UH_KOGWmYw@mail.gmail.com>
2022-03-30 17:25     ` Fwd: " A A via ntg-context
2022-03-30 22:45       ` Aditya Mahajan via ntg-context [this message]
2022-03-31  5:21         ` A A via ntg-context
2022-03-31  5:24           ` A A via ntg-context
2022-03-31  9:18             ` Alain Delmotte via ntg-context
2022-03-31 15:02               ` A A via ntg-context

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.YAK.7.78.908.2203301843210.244301@nqv-guvaxcnq \
    --to=ntg-context@ntg.nl \
    --cc=adityam@umich.edu \
    /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.
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 NNTP newsgroup(s).