ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Giuseppe Bilotta" <oblomov@freemail.it>
Subject: texexec
Date: Sat, 10 Feb 2001 20:02:09 +0100	[thread overview]
Message-ID: <000d01c093b0$4985b340$a3ccfea9@nuovo> (raw)

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


             reply	other threads:[~2001-02-10 19:02 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-10 19:02 Giuseppe Bilotta [this message]
2001-02-11  8:23 ` texexec Marc van Dongen
2001-02-11 21:14 ` texexec Hans Hagen
2001-02-12 16:35 ` texexec Ed L Cashin
2001-02-12 18:48   ` texexec Taco Hoekwater
  -- strict thread matches above, loose matches on Subject: below --
2006-05-04 22:03 texexec Hans Hagen
2006-05-04 23:59 ` texexec Jilani Khaldi
2006-05-05  6:10 ` texexec luigi scarso
2006-05-05 13:26 ` texexec Steve Grathwohl
2006-05-05 13:36 ` texexec Renaud AUBIN
2006-05-05 15:16   ` texexec Hans Hagen
2006-05-05 14:09 ` texexec Steve Peter
2006-05-06 23:01 ` texexec Aditya Mahajan
2006-05-07 18:14   ` texexec Hans Hagen
2006-05-07 18:34     ` texexec Aditya Mahajan
2006-05-07 21:15       ` texexec Hans Hagen
2006-05-08  0:37         ` texexec Aditya Mahajan
2006-05-07 19:10   ` texexec Hans Hagen
2006-05-07 19:29     ` texexec Aditya Mahajan
2006-05-07 19:13   ` texexec Hans Hagen
2006-05-07 19:30     ` texexec Aditya Mahajan
2006-05-07 21:53     ` texexec Mojca Miklavec
2006-05-15 22:55 ` texexec frantisek holop
2006-05-15 23:06   ` texexec Hans Hagen
2006-06-19 21:46 ` texexec John R. Culleton
2006-06-19 21:13   ` texexec Hans Hagen
     [not found] <Pine.LNX.4.44.0307012300450.9436-100000@twain.marshallward .net>
2003-07-02 18:08 ` Texexec Hans Hagen
2003-07-04 23:39   ` Texexec Marshall Ward
     [not found] <"from Raimund.Kohl"@freenet.de>
2003-06-12 13:18 ` texexec Raimund Kohl
2003-06-12 15:01   ` texexec Ed L Cashin
2003-06-14  9:30     ` texexec Hans Hagen
2003-06-14 11:27       ` texexec Siep Kroonenberg
2003-06-13 15:57   ` texexec Raimund Kohl-Fuechsle
2003-06-13 16:00   ` texexec Raimund Kohl
2003-06-12 13:04 texexec Raimund Kohl-Fuechsle
2002-12-09 14:56 texexec Matthew Huggett
2002-12-09 19:25 ` texexec Henning Hraban Ramm
2000-02-08  6:16 TeXexec Dan Seracu
2000-02-08  8:33 ` TeXexec Gilbert van den Dobbelsteen
2000-02-08  9:33   ` TeXexec Dan Seracu
     [not found] <375383E9.3A6BF93E@wxs.nl>
1999-06-01 19:34 ` texexec David Arnold
1999-06-02  7:26   ` texexec Hans Hagen
1999-04-22 12:31 texexec Thomas Esser
1999-04-23  7:09 ` texexec Hans Hagen
1999-04-22 12:13 texexec Thomas Esser
1999-04-22 14:28 ` texexec Taco Hoekwater
1999-04-22  9:05 texexec Erik Frambach
1999-04-22 11:31 ` texexec Erik Frambach
1999-04-22 12:12 ` texexec Taco Hoekwater

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='000d01c093b0$4985b340$a3ccfea9@nuovo' \
    --to=oblomov@freemail.it \
    /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).