comparison mercurial/helptext/flags.txt @ 44933:33ef8841da62

help: explain in `hg help flags` that unambiguous prefixes are allowed I used `hg commit --amend` as an example because that's the most frequently used flag I could think of that doesn't yet have a short form. Differential Revision: https://phab.mercurial-scm.org/D8607
author Martin von Zweigbergk <martinvonz@google.com>
date Wed, 03 Jun 2020 22:07:26 -0700
parents 2e017696181f
children
comparison
equal deleted inserted replaced
44932:03ba7de6a8b9 44933:33ef8841da62
8 any command - those are seen in :hg:`help -v`, and can be specified before or 8 any command - those are seen in :hg:`help -v`, and can be specified before or
9 after the command. 9 after the command.
10 10
11 Every flag has at least a long name, such as --repository. Some flags may also 11 Every flag has at least a long name, such as --repository. Some flags may also
12 have a short one-letter name, such as the equivalent -R. Using the short or long 12 have a short one-letter name, such as the equivalent -R. Using the short or long
13 name is equivalent and has the same effect. 13 name is equivalent and has the same effect. The long name may be abbreviated to
14 any unambiguous prefix. For example, :hg:`commit --amend` can be abbreviated
15 to :hg:`commit --am`.
14 16
15 Flags that have a short name can also be bundled together - for instance, to 17 Flags that have a short name can also be bundled together - for instance, to
16 specify both --edit (short -e) and --interactive (short -i), one could use:: 18 specify both --edit (short -e) and --interactive (short -i), one could use::
17 19
18 hg commit -ei 20 hg commit -ei