From: Hans Hagen <pragma@wxs.nl>
Cc: "Context Support List" <ntg-context@ntg.nl>
Subject: Re: Follow up: Problem installing context with miktex
Date: Mon, 09 Jul 2001 14:26:24 +0200 [thread overview]
Message-ID: <3.0.6.32.20010709142624.01396e20@server-1> (raw)
In-Reply-To: <001001c10865$8c5feb20$8a8a16cb@massey.ac.nz>
At 08:54 PM 7/9/01 +1000, Luis A. Apiolaza wrote:
> Hi, Finally I just installed Miktex 2.1 and modified texexec.rme and
>set the appropriate paths and context is working! Thanks to all for your
>help. I have an additional question: what are context-aware editors that
>people are using under M$ Windows? Looking in the archive and the net, it
>seems that some people use emacs and there is a mention to Texwork. Is the
>latest an editor to use with context or something else? I couldn't find any
> documentation about its use. Thanks in advance, Luis Dr. Luis A.
>Apiolaza CRC for Sustainable Production Forestry School of Plant Science
>University of Tasmania GPO Box 252-55 Hobart Tas 7001 Australia
texwork is "work in progress" and is a perl/tk implementation of the system
we use here; it's a kind of integrated environment
there are winedt env files in the big context zip as well as a vim
highlighting file [simple]; on our site you can find winedt/emacs stuff
from users;
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-07-09 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 10:54 Luis A. Apiolaza
2001-07-09 12:09 ` Eckhart Guthöhrlein
2001-07-09 14:17 ` Hans Hagen
2001-07-10 6:47 ` Eckhart Guthöhrlein
2001-07-09 12:26 ` Hans Hagen [this message]
2001-07-10 6:49 ` Eckhart Guthöhrlein
2001-07-10 7:33 ` Hans Hagen
2001-07-11 12:14 ` Editors Henning Hraban Ramm
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=3.0.6.32.20010709142624.01396e20@server-1 \
--to=pragma@wxs.nl \
--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).