Re: [PATCH v2 2/2] alias: support non-alphanumeric names via subsection syntax

["Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>]

On Tue, Feb 10, 2026, at 19:31, Jonatan Holmgren wrote:
> [snip]
>
> Suggested-by: Jeff King <peff@peff.net>
> Signed-off-by: Jonatan Holmgren <jonatan@jontes.page>
> ---
>  Documentation/config/alias.adoc | 44 +++++++++++++++++++++-----
>  alias.c                         | 45 ++++++++++++++++++++++-----
>  help.c                          | 12 +++++--
>  t/t0014-alias.sh                | 55 +++++++++++++++++++++++++++++++++
>  4 files changed, 137 insertions(+), 19 deletions(-)
>
> diff --git a/Documentation/config/alias.adoc
> b/Documentation/config/alias.adoc
> index 80ce17d2de..17a548cd64 100644
> --- a/Documentation/config/alias.adoc
> +++ b/Documentation/config/alias.adoc
>[snip]
> +# With subsection (allows UTF-8 and special characters)
> +[alias "hämta"]
> +    command = fetch
> +[alias "gömma"]
> +    command = stash
> +----
> ++
> +E.g. after defining `alias.last = cat-file commit HEAD`, the invocation
> +`git last` is equivalent to `git cat-file commit HEAD`. To avoid
> +confusion and troubles with script usage, aliases that
> +hide existing Git commands are ignored except for deprecated
> +commands.  Arguments are split by
> +spaces, the usual shell quoting and escaping are supported.
> +A quote pair or a backslash can be used to quote them.
>  +
>  Note that the first word of an alias does not necessarily have to be a

The HTML output shows the list continuation character (+).

    + Note that the first word of an alias does not ...

>  command. It can be a command-line option that will be passed into the

And there are two more outside this context which I suspect are knock-ons?

    + If the alias expansion is prefixed ..

    ...

    + * Shell commands will be executed ...

See `Documentation/doc-diff master next`.

• master: 7c02d39f (The 6th batch, 2026-02-20)
• next: 4a7958ca (Sync with 'master', 2026-02-20)

> diff --git a/alias.c b/alias.c
>[snip]