From: Ben Knoble Date: Sat, 01 Aug 2026 00:05:45 GMT Subject: Re: Git trailing blank lines feature configuration Message-ID: <06230920-FCA6-495C-BFE5-04DF1CC2A426@gmail.com> In-Reply-To: <5097209.GXAFRqVoOG@cixi> > Le 31 juil. 2026 à 20:55, Thomas Nemeth a écrit : > > 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. I use Vim, too, and I’ve not personally encountered the desire for keeping a blank line at EOF (though occasionally certain operations benefit from placing one there first!). I wonder if you could describe example workflows that lead to this desire? I might learn something, and in exchange, if I see a way to accomplish the same thing with less hassle, I’ll suggest it ;) Cheers