[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGG-pUQMjZWw=ECJ32OMhmKzyTgK64Let1JNkoF7uM72db=MWw@mail.gmail.com>
Date: Mon, 25 Jan 2016 19:24:02 -0300
From: "Geyslan G. Bem" <geyslan@...il.com>
To: Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
linux-usb@...r.kernel.org, Greg KH <gregkh@...uxfoundation.org>,
Alan Stern <stern@...land.harvard.edu>,
Joe Perches <joe@...ches.com>
Subject: Re: [RFC PATCH] codingstyle: improve elisp for a better experience
2016-01-25 17:01 GMT-03:00 Jonathan Corbet <corbet@....net>:
> 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?
Yes, you have a point. I could make the kernel-dot-emacs.txt. Thank
you Jonathan.
About the elisp, the emacs users have any suggestions?
>
> Thanks,
>
> jon
--
Regards,
Geyslan G. Bem
hackingbits.com
Powered by blists - more mailing lists