All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Nemeth <tnemeth@free.fr>
To: Johannes Sixt <j6t@kdbg.org>
Cc: git@vger.kernel.org
Subject: Re: Git trailing blank lines feature configuration
Date: Fri, 31 Jul 2026 13:50:17 +0200	[thread overview]
Message-ID: <5097209.GXAFRqVoOG@cixi> (raw)
In-Reply-To: <d5ec69c8-e441-4134-a6bb-665fc06db187@kdbg.org>

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.



  reply	other threads:[~2026-07-31 11:50 UTC|newest]

Thread overview: 4+ 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 [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=5097209.GXAFRqVoOG@cixi \
    --to=tnemeth@free.fr \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.