Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1808784
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T06:18:24+00:00 2026-05-17T06:18:24+00:00

Ideally I’d like an answer to the title question. However, for my particular case,

  • 0

Ideally I’d like an answer to the title question.

However, for my particular case, I have a Perl script that I want to run from the precommit hook and I’d like to know if Mercurial was invoked with the -A option passed to the commit command (e.g. hg commit -A) and if it wasn’t, is it possible to “pass” it in at that point?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T06:18:24+00:00Added an answer on May 17, 2026 at 6:18 am

    This is going to seem a little silly, but in addition to the precommit hook, there’s a pre-XXXX (and post-XXXX) hook for every command, which gets some different variables:

    pre-<command>

    Run before executing the associated
    command. The contents of the command
    line are passed as $HG_ARGS. Parsed
    command line arguments are passed as
    $HG_PATS and $HG_OPTS. These contain
    string representations of the data
    internally passed to .
    $HG_OPTS is a dictionary of options
    (with unspecified options set to their
    defaults). $HG_PATS is a list of
    arguments. If the hook returns
    failure, the command doesn’t execute
    and Mercurial returns the failure
    code.

    So do a pre-commit hook instead and check those variables.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.