- Jul 7, 2013On 07/07/13 15:26, tux- wrote:
>Oh, does it? Mine (on Linux) doesn't. Try doing a full make (i.e.,
> Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 06:53 Zeit:
>> You should already have it.
> Oh, right, thanks!
> But why does it still "make" 7.3? :-/ (I use MS Windows, VS 2010.)
telling Make to rebuild everything).
Normally, the mere fact that version.h has changed, that it now includes
* VIM_VERSION_NODOT is used for the runtime directory name.
* VIM_VERSION_SHORT is copied into the swap file (max. length is 6 chars).
* VIM_VERSION_MEDIUM is used for the startup-screen.
* VIM_VERSION_LONG is used for the ":version" command and "Vim -h".
#define VIM_VERSION_NODOT "vim74a"
#define VIM_VERSION_SHORT "7.4a"
#define VIM_VERSION_MEDIUM "7.4a BETA"
#define VIM_VERSION_LONG "VIM - Vi IMproved 7.4a BETA (2013 Jul 6)"
#define VIM_VERSION_LONG_DATE "VIM - Vi IMproved 7.4a BETA (2013 Jul 6,
and that version.o depends on both version.c and version.h (which
version.c includes) should make Make launch a compile of version.c, even
in a "partial" build. Of course, if you have changed those very lines in
your "home changes", then…
Are you sure your "current" changeset ("hg log -r ." without the quotes)
is on the default branch and is a descendant of v7-4a-001? To make sure,
enable and use the graphlog extension as I said earlier. If it isn't, then
hg up -r default
# apply your changes again (possibly by hg merge)
hg commit -m 'local changes, as follows: bla bla bla'
No new branch! The next fetch will pull changesets the way they are on
the remote, then merge your changes (it is best to place them somewhere
in the file where there is low risk of bit-rot).
OLD WOMAN: Well, how did you become king, then?
ARTHUR: The Lady of the Lake, her arm clad in the purest shimmering samite,
held Excalibur aloft from the bosom of the water to signify by
Providence ... that I, Arthur, was to carry Excalibur ... That is
why I am your king!
"Monty Python and the Holy Grail" PYTHON (MONTY)
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
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe@....
For more options, visit https://groups.google.com/groups/opt_out.
- << Previous post in topic Next post in topic >>