Loading ...
Sorry, an error occurred while loading the content.

Patch 7.4a.001

Expand Messages
  • Bram Moolenaar
    [Note: mercurial already had this change] Patch 7.4a.001 Problem: Script to update syntax menu is oudated. Solution: Add the missing items. Files:
    Message 1 of 22 , Jul 6, 2013
    • 0 Attachment
      [Note: mercurial already had this change]

      Patch 7.4a.001
      Problem: Script to update syntax menu is oudated.
      Solution: Add the missing items.
      Files: runtime/makemenu.vim


      *** ../vim-7.4a.000/runtime/makemenu.vim 2010-08-04 17:34:32.000000000 +0200
      --- runtime/makemenu.vim 2013-07-06 15:42:18.000000000 +0200
      ***************
      *** 1,6 ****
      " Script to define the syntax menu in synmenu.vim
      " Maintainer: Bram Moolenaar <Bram@...>
      ! " Last Change: 2010 Aug 04

      " This is used by "make menu" in the src directory.
      edit <sfile>:p:h/synmenu.vim
      --- 1,6 ----
      " Script to define the syntax menu in synmenu.vim
      " Maintainer: Bram Moolenaar <Bram@...>
      ! " Last Change: 2013 Jul 06

      " This is used by "make menu" in the src directory.
      edit <sfile>:p:h/synmenu.vim
      ***************
      *** 139,144 ****
      --- 139,145 ----
      SynMenu C.Config.Generic\ Config\ file:conf
      SynMenu C.CRM114:crm
      SynMenu C.Crontab:crontab
      + SynMenu C.CSDL:csdl
      SynMenu C.CSP:csp
      SynMenu C.Ctrl-H:ctrlh
      SynMenu C.Cucumber:cucumber
      ***************
      *** 262,267 ****
      --- 263,273 ----
      SynMenu HIJK.Initng:initng
      SynMenu HIJK.Inittab:inittab
      SynMenu HIJK.Inno\ setup:iss
      + SynMenu HIJK.Innovation\ Data\ Processing.Upstream\ dat:upstreamdat
      + SynMenu HIJK.Innovation\ Data\ Processing.Upstream\ log:upstreamlog
      + SynMenu HIJK.Innovation\ Data\ Processing.Upstream\ Install\ log:upstreaminstalllog
      + SynMenu HIJK.Innovation\ Data\ Processing.Usserver\ log:usserverlog
      + SynMenu HIJK.Innovation\ Data\ Processing.USW2KAgt\ log:usw2kagtlog
      SynMenu HIJK.InstallShield\ script:ishd
      SynMenu HIJK.Interactive\ Data\ Lang:idlang
      SynMenu HIJK.IPfilter:ipfilter
      *** ../vim-7.4a.000/src/version.c 2013-07-06 14:11:48.000000000 +0200
      --- src/version.c 2013-07-06 16:01:55.000000000 +0200
      ***************
      *** 730,731 ****
      --- 730,733 ----
      { /* Add new patch number below this line */
      + /**/
      + 1,
      /**/

      --
      SIGFUN -- signature too funny (core dumped)

      /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      \\\ an exciting new programming language -- http://www.Zimbu.org ///
      \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

      --
      --
      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.
    • tooth pik
      ... it builds and works fine for me one [admittedly trivial] question though: shouldn t it be called 7.4a.0001? -- _|_ _ __|_|_ ._ o| ... -- -- You received
      Message 2 of 22 , Jul 6, 2013
      • 0 Attachment
        On Sat, Jul 06, 2013 at 04:24:58PM +0200, Bram Moolenaar wrote:

        > [Note: mercurial already had this change]

        > Patch 7.4a.001

        it builds and works fine for me

        one [admittedly trivial] question though: shouldn't it be called 7.4a.0001?

        --
        _|_ _ __|_|_ ._ o|
        |_(_)(_)|_| ||_)||<
        |

        --
        --
        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.
      • Taro MURAOKA
        Hi Bram. On mercurial repositry, the patch number 1 is duplicated. Please check here
        Message 3 of 22 , Jul 6, 2013
        • 0 Attachment
          Hi Bram.


          On mercurial repositry, the patch number 1 is duplicated.
          Please check here https://code.google.com/p/vim/source/browse/src/version.c?r=0ddba00c204d855c0b3da30cb338d9bdb0ded847#732

          --
          --
          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.
        • Tony Mechelynck
          ... Mercurial already had it, but there still is a v7-4a-001 changeset on the Mercurial server; the only thing it does is add patch number 1 *twice* in the
          Message 4 of 22 , Jul 6, 2013
          • 0 Attachment
            On 06/07/13 16:24, Bram Moolenaar wrote:
            >
            > [Note: mercurial already had this change]
            >
            > Patch 7.4a.001
            > Problem: Script to update syntax menu is oudated.
            > Solution: Add the missing items.
            > Files: runtime/makemenu.vim

            Mercurial already had it, but there still is a v7-4a-001 changeset on
            the Mercurial server; the only thing it does is add patch number 1
            *twice* in the list of patches in version.c

            Indeed, "hg diff -r v7-4a -r v7-4a-001" produces the following output
            (I'm inserting "as quotation" to avoid spurious line breaks; but this
            means "> " will be inserted in front of each line):

            > diff --git a/.hgtags b/.hgtags
            > --- a/.hgtags
            > +++ b/.hgtags
            > @@ -2646,8 +2646,9 @@ 71859e71b1f902c28b8842bc7092dd155b8c7f88
            > 3dafc80e781b8d5ed12d6107a2c804067aeafd90 v7-3-1307
            > 71e066e10a4789eeb9553aa08f9ca8e7eec96532 v7-3-1308
            > a686295448918b7066bc52e3fd9748e6702c2219 v7-3-1309
            > b49784c49d537fabe083cc3f8cc460629bb6957f v7-3-1310
            > 28e6f5f889683fe161b7bc260bd02b742157fc5b v7-3-1311
            > 80bab8b1a30db72b7eda880b0442ab0b0f4a1611 v7-3-1312
            > afbc9dd67cea81e73d64f7ecce47dfcd35d48865 v7-3-1313
            > 29e57603bf6f3a2e3c178a63d332ed4d2eccfa82 v7-3-1314
            > +6ec6b7ff2d43842d04a8d653356d0ff3850707c0 v7-4a
            > diff --git a/src/version.c b/src/version.c
            > --- a/src/version.c
            > +++ b/src/version.c
            > @@ -724,16 +724,20 @@ static char *(features[]) =
            > # endif
            > #endif
            > NULL
            > };
            >
            > static int included_patches[] =
            > { /* Add new patch number below this line */
            > /**/
            > + 1,
            > +/**/
            > + 1,
            > +/**/
            > 0
            > };
            >
            > /*
            > * Place to put a short description when adding a feature with a patch.
            > * Keep it short, e.g.,: "relative numbers", "persistent undo".
            > * Also add a comment marker to separate the lines.
            > * See the official Vim patches for the diff format: It must use a context of

            Notice the four lines "added" (prefixed with +) in version.c


            Best regards,
            Tony.
            --
            Worst Vegetable of the Year:
            The brussels sprout. This is also the worst vegetable of next
            year.
            -- Steve Rubenstein

            --
            --
            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.
          • tux-
            Can I (somehow) rebase my vim73 repository to vim74? -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the
            Message 5 of 22 , Jul 6, 2013
            • 0 Attachment
              Can I (somehow) rebase my vim73 repository to vim74?

              --
              --
              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.
            • Bram Moolenaar
              ... Thanks for noticing. My script failed the first time and I forgot to correct this part. -- BEDEVERE: How do you know so much about swallows? ARTHUR:
              Message 6 of 22 , Jul 6, 2013
              • 0 Attachment
                Taro Muraoka wrote:

                > On mercurial repositry, the patch number 1 is duplicated.
                > Please check here https://code.google.com/p/vim/source/browse/src/version.c?r=0ddba00c204d855c0b3da30cb338d9bdb0ded847#732

                Thanks for noticing. My script failed the first time and I forgot to
                correct this part.

                --
                BEDEVERE: How do you know so much about swallows?
                ARTHUR: Well you have to know these things when you're a king, you know.
                "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

                /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
                /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
                \\\ an exciting new programming language -- http://www.Zimbu.org ///
                \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

                --
                --
                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.
              • Bram Moolenaar
                ... I m pretty sure that there won t be more than 999 patches for 7.4a. -- Every exit is an entrance into something else. /// Bram Moolenaar --
                Message 7 of 22 , Jul 6, 2013
                • 0 Attachment
                  Toothpik wrote:

                  > On Sat, Jul 06, 2013 at 04:24:58PM +0200, Bram Moolenaar wrote:
                  >
                  > > [Note: mercurial already had this change]
                  >
                  > > Patch 7.4a.001
                  >
                  > it builds and works fine for me
                  >
                  > one [admittedly trivial] question though: shouldn't it be called
                  > 7.4a.0001?

                  I'm pretty sure that there won't be more than 999 patches for 7.4a.

                  --
                  Every exit is an entrance into something else.

                  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
                  /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
                  \\\ an exciting new programming language -- http://www.Zimbu.org ///
                  \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

                  --
                  --
                  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.
                • Zulox4
                  ... The letter a is new, like this it s possible to have a..z (26 char) multiplied by 999 ... -- -- You received this message from the vim_dev maillist. Do
                  Message 8 of 22 , Jul 6, 2013
                  • 0 Attachment
                    On Saturday, July 6, 2013 6:18:44 PM UTC+2, Bram Moolenaar wrote:
                    > Toothpik wrote:
                    >
                    >
                    >
                    > > On Sat, Jul 06, 2013 at 04:24:58PM +0200, Bram Moolenaar wrote:
                    >
                    > >
                    >
                    > > > [Note: mercurial already had this change]
                    >
                    > >
                    >
                    > > > Patch 7.4a.001
                    >
                    > >
                    >
                    > > it builds and works fine for me
                    >
                    > >
                    >
                    > > one [admittedly trivial] question though: shouldn't it be called
                    >
                    > > 7.4a.0001?
                    >
                    >
                    >
                    > I'm pretty sure that there won't be more than 999 patches for 7.4a.
                    >
                    >
                    >
                    > --
                    >
                    > Every exit is an entrance into something else.
                    >
                    >
                    >
                    > /// Bram Moolenaar -- Bram@..olenaar.net -- http://www.Moolenaar.net \\\
                    >
                    > /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
                    >
                    > \\\ an exciting new programming language -- http://www.Zimbu.org ///
                    >
                    > \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

                    The letter "a" is new, like this it's possible to have a..z (26 char) multiplied by 999 ...

                    --
                    --
                    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.
                  • Tony Mechelynck
                    ... With Mercurial, it is (in principle) not possible to rewrite history. My brand-new vim74a clone goes back all the way to 7.0000 alpha, which is when the
                    Message 9 of 22 , Jul 6, 2013
                    • 0 Attachment
                      On 06/07/13 17:58, tux- wrote:
                      > Can I (somehow) rebase my vim73 repository to vim74?
                      >
                      With Mercurial, it is (in principle) not possible to rewrite history. My
                      brand-new vim74a clone goes back all the way to 7.0000 alpha, which is
                      when the Vim source was first brought under Mercurial, and everything
                      in-between is included, and ever will be.

                      Best regards,
                      Tony.
                      --
                      It is true that if your paperboy throws your paper into the bushes for
                      five straight days it can be explained by Newton's Law of Gravity. But
                      it takes Murphy's law to explain why it is happening to you.

                      --
                      --
                      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.
                    • tux-
                      Damn. So I ll have to merge my modifications all manually again? :-/ What s the command to clone vim74 again? -- -- You received this message from the
                      Message 10 of 22 , Jul 6, 2013
                      • 0 Attachment
                        Damn. So I'll have to merge my modifications all manually again? :-/

                        What's the command to clone vim74 again?

                        --
                        --
                        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.
                      • Tony Mechelynck
                        ... No. Your changes can be merged automatically, since v7-4a is the child of v7-3-1314. I have a few changes too (in .hgignore and in src/feature.h), hg
                        Message 11 of 22 , Jul 6, 2013
                        • 0 Attachment
                          On 06/07/13 20:05, tux- wrote:
                          > Damn. So I'll have to merge my modifications all manually again? :-/

                          No. Your changes can be merged automatically, since v7-4a is the child
                          of v7-3-1314. I have a few changes too (in .hgignore and in
                          src/feature.h), "hg fetch --switch-parent" merges them every time I pull
                          new changes (and the way I wrote them, it's very rare that I have to do
                          the merge by hand); they carried over from 7.3.1314 to 7.4a with no
                          special action from me.
                          >
                          > What's the command to clone vim74 again?
                          >
                          If you make a new clone, you'll have the full history of Vim 7.0000,
                          7.0a, ... 7.1, ... 7.2, ... 7.3, ... 7.4a.001, and none of your own changes.


                          Best regards,
                          Tony.
                          --
                          Have you ever noticed that the people who are always trying to tell
                          you, "There's a time for work and a time for play," never find the time
                          for play?

                          --
                          --
                          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.
                        • tux-
                          ... Hmm.. hg: unknown command fetch :-/ -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you
                          Message 12 of 22 , Jul 6, 2013
                          • 0 Attachment
                            Tony Mechelynck schrob am Samstag, 6. Juli 2013 um 20:21 Zeit:

                            > "hg fetch --switch-parent" merges them every time I pull
                            > new changes

                            Hmm..

                            "hg: unknown command 'fetch'" :-/

                            --
                            --
                            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.
                          • Tony Mechelynck
                            ... It s a built-in extension to Mercurial, you have to enable it before you can use it. It does a pull-update or a pull-and-merge (depending of the structure
                            Message 13 of 22 , Jul 6, 2013
                            • 0 Attachment
                              On 06/07/13 20:22, tux- wrote:
                              > Tony Mechelynck schrob am Samstag, 6. Juli 2013 um 20:21 Zeit:
                              >
                              >> "hg fetch --switch-parent" merges them every time I pull
                              >> new changes
                              >
                              > Hmm..
                              >
                              > "hg: unknown command 'fetch'" :-/
                              >

                              It's a built-in extension to Mercurial, you have to enable it before you
                              can use it. It does a pull-update or a pull-and-merge (depending of the
                              structure of your clone) in one operation. See
                              http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial for details.


                              Best regards,
                              Tony.
                              --
                              ARTHUR: ... and I am your king ....
                              OLD WOMAN: Ooooh! I didn't know we had a king. I thought we were an
                              autonomous collective ...
                              "Monty Python and the Holy Grail" PYTHON (MONTY)
                              PICTURES LTD

                              --
                              --
                              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.
                            • tux-
                              Ah, thanks! Now: abort: outstanding uncommitted changes ...? -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply
                              Message 14 of 22 , Jul 6, 2013
                              • 0 Attachment
                                Ah, thanks!

                                Now: "abort: outstanding uncommitted changes"...?

                                --
                                --
                                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.
                              • Tony Mechelynck
                                ... In order to be able to fetch, your clone must be in a stable state, i.e. if you have made changes and want to keep them, you need to commit them. No need
                                Message 15 of 22 , Jul 6, 2013
                                • 0 Attachment
                                  On 06/07/13 20:44, tux- wrote:
                                  > Ah, thanks!
                                  >
                                  > Now: "abort: outstanding uncommitted changes"...?
                                  >
                                  In order to be able to fetch, your clone must be in a "stable" state,
                                  i.e. if you have made changes and want to keep them, you need to commit
                                  them. No need to give them a branch name, the pull will add the new
                                  changesets as children of the same parents they had on the remote repo,
                                  then (if necessary) a merge will add your own changes.

                                  See:
                                  hg help commit
                                  hg help addremove
                                  hg help hgignore
                                  etc.


                                  Best regards,
                                  Tony.
                                  v--
                                  The modern child will answer you back before you've said anything.
                                  -- Laurence J. Peter

                                  --
                                  --
                                  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.
                                • tux-
                                  I see. I commited my changes ( hg commit -m ... ), used hg fetch --switch-parent ... how can I pull 7.4 now? -- -- You received this message from the vim_dev
                                  Message 16 of 22 , Jul 6, 2013
                                  • 0 Attachment
                                    I see.

                                    I commited my changes ("hg commit -m ..."), used hg fetch
                                    --switch-parent ... how can I pull 7.4 now?

                                    --
                                    --
                                    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.
                                  • Tony Mechelynck
                                    ... You should already have it. hg tags ought to show, among others, v7-4a-001 as one of the close ancestors of your tip . Or, enable the graphlog
                                    Message 17 of 22 , Jul 6, 2013
                                    • 0 Attachment
                                      On 06/07/13 21:26, tux- wrote:
                                      > I see.
                                      >
                                      > I commited my changes ("hg commit -m ..."), used hg fetch
                                      > --switch-parent ... how can I pull 7.4 now?
                                      >
                                      You should already have it. "hg tags" ought to show, among others,
                                      "v7-4a-001" as one of the close ancestors of your "tip". Or, enable the
                                      graphlog extension, then "hg glog -l 10" ²will show you how the latest
                                      10 changeset relate to each other in terms of ancestry.

                                      If you have (as I do, see
                                      http://users.skynet.be/antoine.mechelynck/vim/compunix.htm for
                                      Unix-like) a "myenviro" script to set the settings for configure and
                                      make, then (assuming a bash shell)

                                      source myenviro
                                      (make && make install || echo 'exit status' $?) 2>&1 |tee -a make.log

                                      will install the latest vim 7.4a as (by default)
                                      /usr/local/bin/vim # the executable
                                      /usr/local/share/vim/vim74a/*
                                      where that new vim74a directory becomes your new $VIMRUNTIME. Your $VIM
                                      directory (normally /usr/local/share/vim/ under Unix-like) is unchanged,
                                      as is (of course) your $HOME directory, so any user scripts you had will
                                      be kept.

                                      For Windows the details are a little different but the philosophy is the
                                      same.


                                      Best regards,
                                      Tony.
                                      --
                                      Real Users know your home telephone number.

                                      --
                                      --
                                      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.
                                    • tux-
                                      ... Oh, right, thanks! But why does it still make 7.3? :-/ (I use MS Windows, VS 2010.) -- -- You received this message from the vim_dev maillist. Do not
                                      Message 18 of 22 , Jul 7, 2013
                                      • 0 Attachment
                                        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.)

                                        --
                                        --
                                        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.
                                      • Bram Moolenaar
                                        Patch 7.4a.002 Problem: Valgrind errors in test 89. (Simon Ruderich) Solution: Allocate one more byte. (Dominique Pelle) Files: src/misc2.c ...
                                        Message 19 of 22 , Jul 7, 2013
                                        • 0 Attachment
                                          Patch 7.4a.002
                                          Problem: Valgrind errors in test 89. (Simon Ruderich)
                                          Solution: Allocate one more byte. (Dominique Pelle)
                                          Files: src/misc2.c


                                          *** ../vim-7.4a.001/src/misc2.c 2013-07-04 21:14:48.000000000 +0200
                                          --- src/misc2.c 2013-07-07 16:03:35.000000000 +0200
                                          ***************
                                          *** 4712,4718 ****
                                          {
                                          wc_path = vim_strsave(search_ctx->ffsc_wc_path);
                                          temp = alloc((int)(STRLEN(search_ctx->ffsc_wc_path)
                                          ! + (STRLEN(search_ctx->ffsc_fix_path)) - len));
                                          }

                                          if (temp == NULL || wc_path == NULL)
                                          --- 4712,4719 ----
                                          {
                                          wc_path = vim_strsave(search_ctx->ffsc_wc_path);
                                          temp = alloc((int)(STRLEN(search_ctx->ffsc_wc_path)
                                          ! + STRLEN(search_ctx->ffsc_fix_path + len)
                                          ! + 1));
                                          }

                                          if (temp == NULL || wc_path == NULL)
                                          *** ../vim-7.4a.001/src/version.c 2013-07-06 16:21:14.000000000 +0200
                                          --- src/version.c 2013-07-07 16:14:38.000000000 +0200
                                          ***************
                                          *** 730,731 ****
                                          --- 730,733 ----
                                          { /* Add new patch number below this line */
                                          + /**/
                                          + 2,
                                          /**/

                                          --
                                          Kisses may last for as much as, but no more than, five minutes.
                                          [real standing law in Iowa, United States of America]

                                          /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
                                          /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
                                          \\\ an exciting new programming language -- http://www.Zimbu.org ///
                                          \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

                                          --
                                          --
                                          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.
                                        • Tony Mechelynck
                                          ... Oh, does it? Mine (on Linux) doesn t. Try doing a full make (i.e., telling Make to rebuild everything). Normally, the mere fact that version.h has changed,
                                          Message 20 of 22 , Jul 7, 2013
                                          • 0 Attachment
                                            On 07/07/13 15:26, tux- wrote:
                                            >
                                            > 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.)
                                            >
                                            Oh, does it? Mine (on Linux) doesn't. Try doing a full make (i.e.,
                                            telling Make to rebuild everything).

                                            Normally, the mere fact that version.h has changed, that it now includes
                                            the lines

                                            /*
                                            * 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,
                                            compiled "

                                            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).


                                            Best regards,
                                            Tony.
                                            --
                                            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
                                            Divine
                                            Providence ... that I, Arthur, was to carry Excalibur ... That is
                                            why I am your king!
                                            "Monty Python and the Holy Grail" PYTHON (MONTY)
                                            PICTURES LTD

                                            --
                                            --
                                            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.
                                          • tux-
                                            ... hg tags says 7.4 is current. :-/ The hg up command did not change anything, version.h also says 7.4. Hmm. Weird.. -- -- You received this message from
                                            Message 21 of 22 , Jul 7, 2013
                                            • 0 Attachment
                                              Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 16:22 Zeit:

                                              > 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?

                                              "hg tags" says 7.4 is current. :-/
                                              The "hg up" command did not change anything, version.h also says 7.4.

                                              Hmm. Weird..

                                              --
                                              --
                                              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.
                                            • Tony Mechelynck
                                              ... Notwithstanding the email s Subject, this is indeed patch 7.4a.002. Best regards, Tony. -- The doctrine of human equality reposes on this: that there is no
                                              Message 22 of 22 , Jul 7, 2013
                                              • 0 Attachment
                                                On 07/07/13 16:16, Bram Moolenaar wrote:
                                                >
                                                > Patch 7.4a.002
                                                > Problem: Valgrind errors in test 89. (Simon Ruderich)
                                                > Solution: Allocate one more byte. (Dominique Pelle)
                                                > Files: src/misc2.c

                                                Notwithstanding the email's Subject, this is indeed patch 7.4a.002.


                                                Best regards,
                                                Tony.
                                                --
                                                The doctrine of human equality reposes on this: that there is no man
                                                really clever who has not found that he is stupid.
                                                -- Gilbert K. Chesterson

                                                --
                                                --
                                                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.
                                              Your message has been successfully submitted and would be delivered to recipients shortly.