# [PATCH] doc: fix formatting of function-wrap shell alias

3 messages from 2025-09-01 to 2025-09-02. Participants: Kyle E. Mitchell, Jean-Noël AVILA, Junio C Hamano.
Thread: https://gitlist.dev/t/64066

## Kyle E. Mitchell, 2025-09-01 18:04

Subject: [PATCH] doc: fix formatting of function-wrap shell alias
Message-ID: <20250901180419.2212086-1-kyle@kemitchell.com>
URL: https://gitlist.dev/e/20250901180419.2212086-1-kyle%40kemitchell.com

```
Add a missed backtick to the end of a code segment so that it will be
rendered like preceding examples.

I deeply appreciate the thoroughness of this documentation.  I noticed
the formatting discrepancy reading https://git-scm.com/docs/git-config.

Signed-off-by: Kyle E. Mitchell <kyle@kemitchell.com>
---
 Documentation/config/alias.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/config/alias.adoc b/Documentation/config/alias.adoc
index 2c5db0ad84..95825354bf 100644
--- a/Documentation/config/alias.adoc
+++ b/Documentation/config/alias.adoc
@@ -38,6 +38,6 @@ it will be treated as a shell command.  For example, defining
 ** A convenient way to deal with this is to write your script
    operations in an inline function that is then called with any
    arguments from the command-line.  For example `alias.cmd = "!c() {
-   echo $1 | grep $2 ; }; c" will correctly execute the prior example.
+   echo $1 | grep $2 ; }; c"` will correctly execute the prior example.
 ** Setting `GIT_TRACE=1` can help you debug the command being run for
    your alias.
-- 
2.51.0


```

## Jean-Noël AVILA, 2025-09-01 19:17

Subject: Re: [PATCH] doc: fix formatting of function-wrap shell alias
Message-ID: <2796730.mvXUDI8C0e@cayenne>
URL: https://gitlist.dev/e/2796730.mvXUDI8C0e%40cayenne
In-Reply-To: <20250901180419.2212086-1-kyle@kemitchell.com>

```
On Monday, 1 September 2025 20:04:18 CEST Kyle E. Mitchell wrote:
> Add a missed backtick to the end of a code segment so that it will be
> rendered like preceding examples.
> 
> I deeply appreciate the thoroughness of this documentation.  I noticed
> the formatting discrepancy reading https://git-scm.com/docs/git-config.
> 
> Signed-off-by: Kyle E. Mitchell <kyle@kemitchell.com>
> ---
>  Documentation/config/alias.adoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/config/alias.adoc b/Documentation/config/
alias.adoc
> index 2c5db0ad84..95825354bf 100644
> --- a/Documentation/config/alias.adoc
> +++ b/Documentation/config/alias.adoc
> @@ -38,6 +38,6 @@ it will be treated as a shell command.  For example, 
defining
>  ** A convenient way to deal with this is to write your script
>     operations in an inline function that is then called with any
>     arguments from the command-line.  For example `alias.cmd = "!c() {
> -   echo $1 | grep $2 ; }; c" will correctly execute the prior example.
> +   echo $1 | grep $2 ; }; c"` will correctly execute the prior example.
>  ** Setting `GIT_TRACE=1` can help you debug the command being run for
>     your alias.

Obviously correct.

Thanks!




```

## Junio C Hamano, 2025-09-02 16:24

Subject: Re: [PATCH] doc: fix formatting of function-wrap shell alias
Message-ID: <xmqqh5xklt5r.fsf@gitster.g>
URL: https://gitlist.dev/e/xmqqh5xklt5r.fsf%40gitster.g
In-Reply-To: <2796730.mvXUDI8C0e@cayenne>

```
Jean-Noël AVILA <jn.avila@free.fr> writes:

> On Monday, 1 September 2025 20:04:18 CEST Kyle E. Mitchell wrote:
>> Add a missed backtick to the end of a code segment so that it will be
>> rendered like preceding examples.
>> 
>> I deeply appreciate the thoroughness of this documentation.  I noticed
>> the formatting discrepancy reading https://git-scm.com/docs/git-config.
>> 
>> Signed-off-by: Kyle E. Mitchell <kyle@kemitchell.com>
>> ---
>>  Documentation/config/alias.adoc | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/Documentation/config/alias.adoc b/Documentation/config/
> alias.adoc
>> index 2c5db0ad84..95825354bf 100644
>> --- a/Documentation/config/alias.adoc
>> +++ b/Documentation/config/alias.adoc
>> @@ -38,6 +38,6 @@ it will be treated as a shell command.  For example, 
> defining
>>  ** A convenient way to deal with this is to write your script
>>     operations in an inline function that is then called with any
>>     arguments from the command-line.  For example `alias.cmd = "!c() {
>> -   echo $1 | grep $2 ; }; c" will correctly execute the prior example.
>> +   echo $1 | grep $2 ; }; c"` will correctly execute the prior example.
>>  ** Setting `GIT_TRACE=1` can help you debug the command being run for
>>     your alias.
>
> Obviously correct.

Thanks, both of you.

```
