On 19/05/10 14:29, Xavier de Gaye wrote:
On Wed, May 19, 2010 at 12:34 PM, Tony Mechelynck wrote:
...
.... The problem with that is that though it
is possible to say "this is the same revision as that", it is not obvious,
when different, to say which is the latest one. For that we would need a
time reference or something.
...
This may be handled with a mercurial hook that creates a source file
(after each commit or update command) defining a variable whose value
is the hash of the last changeset. With this source file built into
vim, the hash value could then be printed with the ':version' command,
for example.
This is better explained in
http://hgbook.red-bean.com/read/handling-repository-events-with-hooks.html
Xavier
Well, that is interesting; the idea sounds like the Mercurial changeset
which recent versions of Mozilla applications (Firefox, Thunderbird,
SeaMonkey, ...) display near the top of the about:buildconfig page, e.g.
the part after the last slash in
Source
Built from http://hg.mozilla.org/mozilla-central/rev/0459345d8026
(For Thunderbird you need to set about:buildconfig as a "Mail Start
Page" to see it.)
But even if I patched version.c to add one more line to the output of
":version", for me the latest changeset would always be my latest commit
(usually a merge, unless I recently made some new local changes), and
that would not be relevant to you all. I can do with typing "hg tip"
(or, after local changes, "hg log -l <number> -f" with a well-chosen
<number>) to get (by copy-paste from xterm etc.) the latest changeset
made by Bram, which would be the one just before my latest merge.
Best regards,
Tony.
--
Usage: fortune -P [] -a [xsz] [Q: [file]] [rKe9] -v6[+] dataspec ...
inputdir
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
