From: Tobias Burnus <burnus@gmx.de>
Cc: ntg-context@ntg.nl
Subject: Re: getting context's version
Date: Fri, 20 Sep 2002 11:32:59 +0200 [thread overview]
Message-ID: <3D8AEB4B.A13D28E8@gmx.de> (raw)
In-Reply-To: <5.1.0.14.1.20020520105456.01fd7cd8@server-1>
Hi,
Hans Hagen wrote:
> >Something like this would be good to have in the context core. (watch
> >the *like this*).
> right, needs some thinking -)
> texexec --version
Given that this takes rather long, can we have something kike:
texexec --allversions
or so?
> >Is that doable?
> sure, see attached version.pl
> this is windows, so can you sort out the > redirection alternative for unix?
This is rather Unix which can also be used under Windows ;-)
I had to change texexec.tmp in something different since texexec
insisted to create texexec.tmp itself ...
Then it worked.
How about adding a check whether cont-?? exists before calling texexec?
(de, cz etc. are also missing)
Plus: How about running texexec --once and optaining the version number
for texutil by running texutil --version? The texexec version could be
inserted directly which could save some additional µs.
Tobias
--
This above all: To thine own self be true / And it must follow as
the night the day / Thou canst not then be false to any man.
next prev parent reply other threads:[~2002-09-20 9:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 10:07 Wybo Dekker
2002-09-17 18:00 ` Tobias Burnus
2002-09-17 18:23 ` Wybo Dekker
2002-09-18 6:57 ` Hans Hagen
2002-09-18 8:41 ` Tobias Burnus
2002-09-18 8:59 ` Wybo Dekker
2002-09-18 9:17 ` Tobias Burnus
2002-09-18 9:47 ` Taco Hoekwater
2002-09-18 15:28 ` Wybo Dekker
2002-09-19 18:41 ` Simon Pepping
2002-09-20 8:06 ` Taco Hoekwater
2002-05-20 8:56 ` Hans Hagen
2002-09-20 9:32 ` Tobias Burnus [this message]
2002-05-20 14:42 ` Hans Hagen
2002-09-20 17:55 ` Henning Hraban Ramm
2002-09-21 17:29 ` Simon Pepping
2002-09-18 9:43 ` Taco Hoekwater
2002-09-17 18:28 ` Taco
2002-09-17 21:20 ` Wybo Dekker
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=3D8AEB4B.A13D28E8@gmx.de \
--to=burnus@gmx.de \
--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).