linux-kernel - Re: [RFC PATCH] codingstyle: improve elisp for a better experience

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: <20160125130138.6932dda8@lwn.net>
Date:	Mon, 25 Jan 2016 13:01:38 -0700
From:	Jonathan Corbet <corbet@....net>
To:	"Geyslan G. Bem" <geyslan@...il.com>
Cc:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org, gregkh@...uxfoundation.org,
	stern@...land.harvard.edu, joe@...ches.com
Subject: Re: [RFC PATCH] codingstyle: improve elisp for a better experience

On Thu, 21 Jan 2016 22:18:30 -0300
"Geyslan G. Bem" <geyslan@...il.com> wrote:

> This patch does use of more emacs functionalities which deliver to the
> user indentation, commenting and white space highlighting.

So perhaps it's just me, but that's an awful lot of elisp code for readers
to wade through; many of those readers will not be all that interested in
it.

Can I suggest an alternative?  Make a kernel-dot-emacs.txt in a form that
interested people can pull it (nearly) directly into their .emacs files,
then add a reference to the CodingStyle document.  That makes the stuff
available for interested developers without rubbing everybody's noses in
it.  Make sense?

Thanks,

jon