help: do not show full help text for command on option errors Example $ hg clone --jump foo bar hg clone: option --jump not recognized hg clone [OPTION]... SOURCE [DEST] make a copy of an existing repository options: -U --noupdate the clone will include an empty working copy (only a repository) -u --updaterev REV revision, tag or branch to check out -r --rev REV [+] include the specified changeset -b --branch BRANCH [+] clone only the specified branch --pull use pull protocol to copy metadata --uncompressed use uncompressed transfer (fast over LAN) -e --ssh CMD specify ssh command to use --remotecmd CMD specify hg command to run on the remote side --insecure do not verify server certificate (ignoring web.cacerts config) [+] marked option can be specified multiple times use "hg help clone" to show the full help text Motivation for this change If the user already has specified the command, he probably already knows the command to some extent. Apparently, he has a problem with the options, so we show him just the synopsis with the short help and the details about the options, with a hint on the last line how to get the full help text. Why is Mercurial better with this change? Experts who just forgot about the details of an option don't get that much text thrown at them, while the newbies still get a hint on the last line how to get the full help text.

     1

  $ hg init

     2

  $ echo This is file a1 > a

     3

  $ echo This is file b1 > b

     4

  $ hg add a b

     5

  $ hg commit -m "commit #0"

     6

  $ echo This is file b22 > b

     7

  $ hg commit -m "comment #1"

     8

  $ hg update 0

     9

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    10

  $ rm b

    11

  $ hg commit -A -m "comment #2"

    12

  removing b

    13

  created new head

    14

  $ hg update 1

    15

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    16

  $ hg update

    17

  abort: crosses branches (merge branches or use --check to force update)

    18

  [255]

    19

  $ hg update -c

    20

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved

    21

  $ mv a c

    22

    23

In theory, we shouldn't need the "-y" below, but it prevents this test

    24

from hanging when "hg update" erroneously prompts the user for "keep

    25

or delete".

    26

    27

Should abort:

    28

    29

  $ hg update -y 1

    30

  abort: crosses branches (merge branches or use --clean to discard changes)

    31

  [255]

    32

  $ mv c a

    33

    34

Should succeed:

    35

    36

  $ hg update -y 1

    37

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved