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

Re: runtime/doc/tags under Mercurial control

Expand Messages
  • Manuel Ortega
    ... This annoys me to no end also. Fortunately, I think I ve found a solution. One can make use of mercurial s hooks. Add the following to the hgrc file
    Message 1 of 6 , May 21 11:28 AM
    • 0 Attachment
      On Saturday, May 18, 2013 7:15:27 AM UTC-4, Xavier de Gaye wrote:
      > runtime/doc/tags is under Mercurial control:
      >
      > $ hg locate runtime/doc/tags
      > runtime/doc/tags
      >
      > This file is automatically generated during vim build.
      > It is annoying to have it appear sometimes in the output of 'hg status'
      > or when creating a patch with 'hg diff'. You must revert it first
      > then. I believe it should be removed from the repository.

      This annoys me to no end also. Fortunately, I think I've found a solution. One can make use of mercurial's hooks. Add the following to the hgrc file inside your clone's .hg directory:

      [hooks]
      pre-status = hg revert runtime/doc/tags
      pre-update = hg revert runtime/doc/tags

      This now means that automatically, before any 'hg stat' or before any 'hg update', the relevant revert operation will be done for you.

      (I know that one of hg's hooks is 'preupdate', but that didn't work if there was also the pre-status hook installed, because it created an unresolvable file locking issue. So keep it 'pre-update' rather than 'preupdate'.)

      If anyone discovers an additional hook for which it might be useful to run the revert op, let the list know :)

      -Manny

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