Received-SPF: pass (google.com: domain of linux-kernel+bounces-199136-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Precedence: bulk
MIME-Version: 1.0
References: <20230601075333.14021-1-ihuguet@redhat.com> <CAMZ6RqLoRVHD_M8Jh2ELurhL8E=HWt2DZZFGQvmfFyxKjtNKhg@mail.gmail.com>
 <874jiikr6e.fsf@meer.lwn.net> <CAMZ6RqLJmTjM0dYvixMEAo+uW+zfhdL1n4rnajsHCZcq971oRA@mail.gmail.com>
 <CACT4oudYAK07+PJzJMhTazKe3LP-F4tpQf8CF0vs1pJLEE_4aA@mail.gmail.com>
 <CAK7LNATqNNVX8ECNoO82kY503ArfRPa9GdbYd9tOok_6tGOsew@mail.gmail.com>
 <thbrfziusf37nj5mwsj2a6zmjtenj5b5vhzwu2z5zkhr7ajsg6@whvx46y6mxbz> <20240603121853.GA19897@nvidia.com>
In-Reply-To: <20240603121853.GA19897@nvidia.com>
From: Mateusz Guzik <mjguzik@gmail.com>
Date: Mon, 3 Jun 2024 14:52:18 +0200
Message-ID: <CAGudoHEe=AiRpkyLJTZzU8MtiGC86Kivbyi1xF-Hh0hGJKWhCg@mail.gmail.com>
Subject: Re: [PATCH v4] Add .editorconfig file for basic formatting
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>, =?UTF-8?B?w43DsWlnbyBIdWd1ZXQ=?= <ihuguet@redhat.com>, 
	Vincent MAILHOL <mailhol.vincent@wanadoo.fr>, Jonathan Corbet <corbet@lwn.net>, ojeda@kernel.org, 
	danny@kdrag0n.dev, mic@digikod.net, linux-kernel@vger.kernel.org, 
	joe@perches.com, linux@rasmusvillemoes.dk, willy@infradead.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 3, 2024 at 2:18=E2=80=AFPM Jason Gunthorpe <jgg@nvidia.com> wro=
te:
>
> On Sun, Jun 02, 2024 at 05:30:51PM +0200, Mateusz Guzik wrote:
>
> > As is I think the config mostly gets in the way and most people have a
> > setup which does not use it (for example my vim does not). Alternativel=
y
> > maye it is neovim which is overzalous here and other editors don't trea=
t
> > the entire file. If there is a way to convince the thing to only tend t=
o
> > whitespace issues in edited lines that would be great.
>
> Yes, I think that is quite overzealous, I'd view it as a vim issue.
>

I don't know about vim specifically, it was neovim here, for the record.

Anyhow I put on latex gloves and typed in "apt install emacs", added
the plugin as documented on github
(https://github.com/editorconfig/editorconfig-emacs + entries to
.emacs.d/init.el) and got precisely the same behavior.

There is no way I'm trying to other editors.

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.

Note my vim does not either, I only ran into it after experimenting with ne=
ovim.

--=20
Mateusz Guzik <mjguzik gmail.com>