From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context <ntg-context@ntg.nl>
Subject: Re: Versionnumbers
Date: Thu, 12 Jul 2001 09:17:36 +0200 [thread overview]
Message-ID: <3.0.6.32.20010712091736.019cd600@server-1> (raw)
In-Reply-To: <Pine.LNX.4.21.0107112252540.3379-100000@hahepc1.hahe>
At 11:03 PM 7/11/01 +0200, Hartmut Henkel wrote:
>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.
Where is this line put? At the top of a file? In a separate file? In
principle reading such a line could be automated [i.e. hooked into \starttext]
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-07-12 7:17 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 ` Versionnumbers Hartmut Henkel
2001-07-12 7:17 ` Hans Hagen [this message]
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=3.0.6.32.20010712091736.019cd600@server-1 \
--to=pragma@wxs.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).