ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Eckhart Guthöhrlein" <eckhart_guthoehrlein@public.uni-hamburg.de>
Cc: "Luis A. Apiolaza" <luis.apiolaza@utas.edu.au>,
	ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: Follow up: Problem installing context with miktex
Date: Tue, 10 Jul 2001 08:47:54 +0200	[thread overview]
Message-ID: <5.1.0.14.0.20010710080856.00a9cdf8@public.uni-hamburg.de> (raw)
In-Reply-To: <3.0.6.32.20010709161742.0133e9f0@server-1>

At 16:17 09.07.2001 +0200, Hans Hagen wrote:
>At 02:09 PM 7/9/01 +0200, Eckhart Guthöhrlein wrote:
> >
> >I've been using winedt with latex for several years now. Some quick
> >adaptions enabled me to use context quite comfortably, and I'm satisfied
> >for now. The project setup, however, is very latex-oriented, and I don't
> >know yet if or how it is possible to adjust this. I know a few people using
> >emacs, but nobody who is doing context. I didn't have time to look at
> >texwork yet, so I can't comment on it. Not really a helpful message, but
> >the best I can offer... Just try!
>
>for most cases, it's enough to add processing entries like :
>
>texexec --pdf --once <filename>
>
>texexec --pdf <filename>

Yes, that's what I have done, too. Let me clarify the 'project setup'. I 
was referring to possibilities concerning documents split up into several 
files. Winedt has a rather nice feature for this: you set the main file, 
and winedt finds the included files, gathers information about sectioning, 
bib items, references etc. The document structure is displayed graphically 
as a tree, so you can browse it quickly. But it seems that winedt searches 
for specific latex commands like \input{...}, \ref, \label etc. As most 
things in winedt, this can be customized to search for context commands, 
but this will surely be rather time-consuming. If I do it some day, I will 
make the resulting files available, but I don't promise anything... If 
anybody has done it, I would be very interested.

Eckhart


  reply	other threads:[~2001-07-10  6:47 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 [this message]
2001-07-09 12:26 ` Hans Hagen
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=5.1.0.14.0.20010710080856.00a9cdf8@public.uni-hamburg.de \
    --to=eckhart_guthoehrlein@public.uni-hamburg.de \
    --cc=luis.apiolaza@utas.edu.au \
    --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).