linux-kernel - Re: [PATCH v4] Add .editorconfig file for basic formatting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGudoHEe=AiRpkyLJTZzU8MtiGC86Kivbyi1xF-Hh0hGJKWhCg@mail.gmail.com>
Date: Mon, 3 Jun 2024 14:52:18 +0200
From: Mateusz Guzik <mjguzik@...il.com>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: 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 2:18 PM Jason Gunthorpe <jgg@...dia.com> wrote:
>
> 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). Alternatively
> > maye it is neovim which is overzalous here and other editors don't treat
> > the entire file. If there is a way to convince the thing to only tend to
> > 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 neovim.

-- 
Mateusz Guzik <mjguzik gmail.com>