From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/4011 Path: main.gmane.org!not-for-mail From: "Giuseppe Bilotta" Newsgroups: gmane.comp.tex.context Subject: texexec Date: Sat, 10 Feb 2001 20:02:09 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <000d01c093b0$4985b340$a3ccfea9@nuovo> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035394707 22050 80.91.224.250 (23 Oct 2002 17:38:27 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:38:27 +0000 (UTC) Original-To: "ConTeXt" Xref: main.gmane.org gmane.comp.tex.context:4011 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:4011 Hello, I'm getting so used to ConTeXt that I sometime run texexec on my LaTeX documents. So I found that it would be nice if texexec had (possibly limited) support for non-ConTeXt format, especially plain and LaTeX. I could then link .tex files to texexec without worries. E.g., when texexec recognizing a LaTeX document, it simply bails out; it would be nice if it closed the cont-?? session and started a latex session (possibly running enough times to fix cross-refs, plus running bibtex and makeindex etc---and stopping after no more than 10 --configurable-- runs, to prevent hangups when non-converging LaTeX documents are parsed; such features are implemented in the MiKTeX program texify). Plain support would be even less mess. Is it much work to do? Recognizing a format should not be much work, especially if using well-behaved distributions AND well-behaved files that use the %&fmtname metacommand. Well, LaTeX files can be recognized by \documentclass, anyway. And the user could always force in some way the format in case of misrecognitions. Giuseppe Bilotta Using Microsoft products is like having sex without condoms---but much less pleasurable