From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: cygwin/tetex or miktex?
Date: 10 Oct 2004 22:57:32 +0200 [thread overview]
Message-ID: <m2vfdiz3yb.fsf@levana.de> (raw)
In-Reply-To: <kx9is9ker63.fsf@panix5.panix.com> (rb@panix.com's message of "08 Oct 2004 19:17:08 -0400")
Hello rb,
> Is one of these two preferable when running ConTeXt on windows?
please don't use the subject alone, it is confusing.
You can also use fptex (or texlive). I'd prefer fptex over miktex over
tetex/cygwin. But I am not the person to ask, since I haven't seen a
windows system in a while. Just my impression from reading some
mailing lists and news groups. You might think of posting your
experience to this list.
Patrick
--
ConTeXt wiki: http://contextgarden.net
next prev parent reply other threads:[~2004-10-10 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 23:17 rb
2004-10-10 20:57 ` Patrick Gundlach [this message]
2004-10-10 21:07 ` Henning Hraban Ramm
2004-10-11 6:49 ` Mari Voipio
2004-10-11 8:47 ` Patrick Gundlach
2004-10-11 7:53 ` 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=m2vfdiz3yb.fsf@levana.de \
--to=patrick@gundla.ch \
--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).