From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: Re: Overwritten metapost files
Date: Fri, 28 May 2004 21:27:43 +0200 [thread overview]
Message-ID: <17900CC4-B0DD-11D8-B28B-0030659899AA@fiee.net> (raw)
In-Reply-To: <20040528081625.GB4964@puritan.pcp.ath.cx>
Am Freitag, 28.05.04, um 10:16 Uhr (Europe/Zurich) schrieb Nikolai
Weibull:
> Probably not as good a reason as I think, but yes, the reason being
> that
> I want all texexec output to go into a separate directory. My
> directory
Did you try
texexec myfile --result=output/myfile
?
Grüßlis vom Hraban!
--
http://www.fiee.net/texnique/
next prev parent reply other threads:[~2004-05-28 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 15:47 Nikolai Weibull
2004-05-27 20:48 ` Hans Hagen
2004-05-28 8:16 ` Nikolai Weibull
2004-05-28 19:27 ` Henning Hraban Ramm [this message]
2004-05-29 9:36 ` Nikolai Weibull
2004-05-29 9:47 ` Patrick Gundlach
2004-05-29 10:01 ` Nikolai Weibull
2004-05-29 10:11 ` Patrick Gundlach
2004-05-29 12:55 ` Maurice Diamantini
2004-06-01 18:45 ` Hans Hagen
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=17900CC4-B0DD-11D8-B28B-0030659899AA@fiee.net \
--to=hraban@fiee.net \
--cc=ntg-context@ntg.nl \
/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).