From: Hartmut Henkel <hartmut_henkel@gmx.de>
Cc: ntg-context <ntg-context@ntg.nl>
Subject: Re: Versionnumbers
Date: Wed, 11 Jul 2001 23:03:15 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0107112252540.3379-100000@hahepc1.hahe> (raw)
In-Reply-To: <009a01c10958$c6640420$a7a5e0d5@pandora.be>
You might use `rcs', revision control system. This stamps your files
with an Id string, containing filename, -version, -date, creator...
You submit e. g. the file foo.tex by ci foo.tex. You get the new version
for editing by typing co -l foo.tex
In plain TeX the following macro scans the Id string, when you have
initially included a line \scanrcs $Id$ into your input file:
% begin of file foo.tex
\def\scanrcs $#1 #2,v #3 #4/#5/#6 #7 #8 #9 ${%
\def\fileversion{#3}
\def\filedate{#4#5#6} % Or whatever date format you like
}
\scanrcs $Id: foo.tex,v 1.1 2001/07/11 20:49:46 hahe Exp hahe $
\fileversion
\bye
% end of file foo.tex
E. g. this prints `1.1', the current version.
Should be transferable also to ConTeXt, but don't have experience with
it.
Have fun!
Hartmut
On Tue, 10 Jul 2001, Frans Goddijn wrote:
> I think a current-date/time/seconds line in basic TeX code would
> do that unless you compile several times per second ;-)))
>
> I'm trying to keep track of the versions of my documents. Is it
> possible to print the number of times a file has been generated in a
> title or a header?
> Or, is there some other way to generate versionnumbers?
------------------------------------------------------------------------
Dr.-Ing. Hartmut Henkel
In den Auwiesen 6, D-68723 Oftersheim, Germany
E-Mail: hartmut_henkel@gmx.de
http://www.circuitwizard.de
------------------------------------------------------------------------
next prev parent reply other threads:[~2001-07-11 21:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 15:30 Versionnumbers Hokojoku, Bert
2001-07-10 15:55 ` Versionnumbers Frans Goddijn
2001-07-11 21:03 ` Hartmut Henkel [this message]
2001-07-12 7:17 ` Versionnumbers Hans Hagen
2001-07-12 19:00 ` Versionnumbers Hartmut Henkel
2001-07-10 16:34 ` Versionnumbers 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=Pine.LNX.4.21.0107112252540.3379-100000@hahepc1.hahe \
--to=hartmut_henkel@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).