Mercurial > hg
diff tests/test-help.t @ 39338:fb9ee1ba5e42
test-help: add tests showing that sections can't be filtered by dotted name
author | Yuya Nishihara <yuya@tcha.org> |
---|---|
date | Sun, 05 Aug 2018 12:48:02 +0900 |
parents | 828a45233036 |
children | d30867a745a1 |
line wrap: on
line diff
--- a/tests/test-help.t Sat Aug 18 08:41:36 2018 +0200 +++ b/tests/test-help.t Sun Aug 05 12:48:02 2018 +0900 @@ -1340,6 +1340,68 @@ "smtp.host" Host name of mail server, e.g. "mail.example.com". + +Test section name with dot + + $ hg help config.ui.username + "auth.username" + Optional. Username to authenticate with. If not given, and the remote + site requires basic or digest authentication, the user will be + prompted for it. Environment variables are expanded in the username + letting you do "foo.username = $USER". If the URI includes a username, + only "[auth]" entries with a matching username or without a username + will be considered. + + "smtp.username" + Optional. User name for authenticating with the SMTP server. (default: + None) + + "ui.username" + The committer of a changeset created when running "commit". Typically + a person's name and email address, e.g. "Fred Widget + <fred@example.com>". Environment variables in the username are + expanded. + + (default: "$EMAIL" or "username@hostname". If the username in hgrc is + empty, e.g. if the system admin set "username =" in the system hgrc, + it has to be specified manually or in a different hgrc file) + + + $ hg help config.annotate.git + "diff.git" + Use git extended diff format. + + + $ hg help config.update.check + "merge-tools.check" + A list of merge success-checking options: + + "changed" + Ask whether merge was successful when the merged file shows no + changes. + + "conflicts" + Check whether there are conflicts even though the tool reported + success. + + "prompt" + Always prompt for merge success, regardless of success reported by + tool. + + + $ hg help config.commands.update.check + "commands.update.check" + Determines what level of checking 'hg update' will perform before + moving to a destination revision. Valid values are "abort", "none", + "linear", and "noconflict". "abort" always fails if the working + directory has uncommitted changes. "none" performs no checking, and + may result in a merge with uncommitted changes. "linear" allows any + update as long as it follows a straight line in the revision history, + and may trigger a merge with uncommitted changes. "noconflict" will + allow any update which would not trigger a merge with uncommitted + changes, if any are present. (default: "linear") + + Unrelated trailing paragraphs shouldn't be included $ hg help config.extramsg | grep '^$'