Git trailing blank lines feature configuration

Git trailing blank lines feature configuration

[Thomas Nemeth]

    Hi !

    I have the habit to keep 1 blank line at the end of my files. To me,
    it eases the EOF modifications (selecting code blocks, pasting them)
    in vim.

    Note that I still want to remove blanks at EOL. But I'd like to keep
    1 blank trailing line. I still can, of course, but the diff still
    shows me a red "+"...

    Would it be possible to have a configuration option to avoid warnings
    (because I see that as a warning) about trailing blank lines ?

    Thanks

Thomas.

Re: Git trailing blank lines feature configuration

[Johannes Sixt]

Am 31.07.26 um 12:19 schrieb Thomas Nemeth:
>     I have the habit to keep 1 blank line at the end of my files. To me,
>     it eases the EOF modifications (selecting code blocks, pasting them)
>     in vim.

(Call this is [x].)

>     Would it be possible to have a configuration option to avoid warnings
>     (because I see that as a warning) about trailing blank lines ?
Hearing the first time that an extra blank line at EOF is necessary or
useful. Would the correct question then perhaps be: how do you all
handle [x] without an extra blank line at EOF?

That said, are you looking to disable blank-at-eof from core.whitespace?
Collect all "enabled by default" except this one from [*].

[*]
https://git-scm.com/docs/git-config#Documentation/git-config.txt-corewhitespace

-- Hannes

Re: Git trailing blank lines feature configuration

[Thomas Nemeth]

Le vendredi 31 juillet 2026, 13:08 Johannes Sixt a écrit :
> Am 31.07.26 um 12:19 schrieb Thomas Nemeth:
> >     I have the habit to keep 1 blank line at the end of my files. To
> >     me,
> >     it eases the EOF modifications (selecting code blocks, pasting
> >     them)
> >     in vim.
> 
> (Call this is [x].)
> 
> >     Would it be possible to have a configuration option to avoid
> >     warnings
> >     (because I see that as a warning) about trailing blank lines ?
> 
> Hearing the first time that an extra blank line at EOF is necessary or
> useful. Would the correct question then perhaps be: how do you all

    I wouldn't say necessary, of course. It's -- at least -- my
    preference. For _my_ use case, it's useful. When I move code
    around, and that code is at the end of the file or to be put
    at the end of the file, I find it easier to already have a
    blank line there. That is... Because that's how I use vim to
    code.


> handle [x] without an extra blank line at EOF?
> 
> That said, are you looking to disable blank-at-eof from core.whitespace?
> Collect all "enabled by default" except this one from [*].
> 
> [*]
> https://git-scm.com/docs/git-config#Documentation/git-config.txt-corewhi
> tespace

    -_-;
    indeed.

    ```
    git config --global core.whitespace "-blank-at-eof"
    ```

-- 
Thomas.

Re: Git trailing blank lines feature configuration

[Junio C Hamano]

Thomas Nemeth <tnemeth@free.fr> writes:

>     Hi !
>
>     I have the habit to keep 1 blank line at the end of my files. To me,
>     it eases the EOF modifications (selecting code blocks, pasting them)
>     in vim.
>
>     Note that I still want to remove blanks at EOL. But I'd like to keep
>     1 blank trailing line. I still can, of course, but the diff still
>     shows me a red "+"...
>
>     Would it be possible to have a configuration option to avoid warnings
>     (because I see that as a warning) about trailing blank lines ?
>
>     Thanks
>
> Thomas.

Would it be possible with the current system?  No.

Would it be possible to add such a new feature?  If designed well,
perhaps.

Things to consider (though not exhaustive) include:

 - What mechanism should this modify?

 - What should the new option be called?

 - Do we only need to accommodate those who want one trailing blank
   line?  What about those who want two?  Three?

Thanks.