From: Gerben Wierda <Gerben.Wierda@rna.nl>
Subject: Re: texversion
Date: Mon, 16 Jan 2006 23:13:36 +0100 [thread overview]
Message-ID: <8CAFAADA-6F24-4E37-99CA-401116EE6BB3@rna.nl> (raw)
In-Reply-To: <43CAB91F.2040106@elvenkind.com>
In cases like these I generally do something like this: change the
obsolete command to display a warning (or in this release a warning
and the exec texexec --version, then a year later only the warning,
then later the command disappears altogether.)
G
On 15 Jan 2006, at 22:05, Taco Hoekwater wrote:
> Hans van der Meer wrote:
>> When running the command "texversion" it used to give nice and
>> clean compact output.
>
> The functionality of texversion has been added to regular texexec,
> and development has stopped. Please forget about the standalone
> texversion command and use
> texexec --version
> instead.
>
> Cheers, taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2006-01-16 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 20:20 texversion Hans van der Meer
2006-01-15 21:05 ` texversion Taco Hoekwater
2006-01-16 22:13 ` Gerben Wierda [this message]
2006-01-15 21:33 ` texversion Hans Hagen
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=8CAFAADA-6F24-4E37-99CA-401116EE6BB3@rna.nl \
--to=gerben.wierda@rna.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).