From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Thomas Nemeth <tnemeth@free.fr>, git@vger.kernel.org
Subject: Re: Git trailing blank lines feature configuration
Date: Fri, 31 Jul 2026 11:49:25 -0700 [thread overview]
Message-ID: <xmqq33wzc7uy.fsf@gitster.g> (raw)
In-Reply-To: <d5ec69c8-e441-4134-a6bb-665fc06db187@kdbg.org> (Johannes Sixt's message of "Fri, 31 Jul 2026 13:08:49 +0200")
Johannes Sixt <j6t@kdbg.org> writes:
> 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
Ah, if "I want a configuration that does not complain when it sees
any number (including zero) of blank lines" is what is asked for,
then yes, 'blank-at-eof' would be sufficient.
I misread the request as "I want it to complain if there is not
exactly one blank line at the end" (i.e., zero blank lines will be
flagged as not vi-friendly and two or more blank lines will be
flagged as excess blank lines at the end). That is not something
'blank-at-eof' would help you achieve.
next prev parent reply other threads:[~2026-07-31 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 10:19 Git trailing blank lines feature configuration Thomas Nemeth
2026-07-31 11:08 ` Johannes Sixt
2026-07-31 11:50 ` Thomas Nemeth
2026-07-31 18:49 ` Junio C Hamano [this message]
2026-07-31 15:50 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq33wzc7uy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=tnemeth@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox