[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGudoHEQ9ZDLJ5Dhjg=9Y25wmoef4GpDNL5XBZEk57KCtMHUYg@mail.gmail.com>
Date: Mon, 3 Jun 2024 17:09:09 +0200
From: Mateusz Guzik <mjguzik@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Jason Gunthorpe <jgg@...dia.com>, Masahiro Yamada <masahiroy@...nel.org>,
Íñigo Huguet <ihuguet@...hat.com>,
Vincent MAILHOL <mailhol.vincent@...adoo.fr>, Jonathan Corbet <corbet@....net>, ojeda@...nel.org,
danny@...ag0n.dev, mic@...ikod.net, linux-kernel@...r.kernel.org,
joe@...ches.com, linux@...musvillemoes.dk, willy@...radead.org
Subject: Re: [PATCH v4] Add .editorconfig file for basic formatting
On Mon, Jun 3, 2024 at 3:38 PM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
>
> On Mon, Jun 3, 2024 at 2:52 PM Mateusz Guzik <mjguzik@...il.com> wrote:
> >
> > At this point I suspect this *is* the intended behavior and other
> > people don't run into it because their editor does not look at
> > .editorconfig to begin with.
>
> This is https://github.com/editorconfig/editorconfig/issues/208 -- a
> `modified` value is proposed for just trimming modified lines.
>
> Given the latest version of the specification, it sounds to me like
> the intention is to trim all lines: "... to remove all whitespace
> characters ... in the file".
>
Looks like a dead report.
I suggest someone whacks this file or at least moves it away from top
of the repo (somewhere into Documentation maybe?)
I did my civic duty. I'm disabling the file in my local neovim config,
so the entire ordeal is no longer my problem.
Cheers,
--
Mateusz Guzik <mjguzik gmail.com>
Powered by blists - more mailing lists