public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jean Delvare <jdelvare@suse.de>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Lindent: Handle missing indent gracefully
Date: Sat, 11 Jul 2015 05:56:37 -0700	[thread overview]
Message-ID: <1436619397.2711.19.camel@perches.com> (raw)
In-Reply-To: <20150710143732.108f19c660402c8dedc18263@linux-foundation.org>

On Fri, 2015-07-10 at 14:37 -0700, Andrew Morton wrote:
> On Fri, 10 Jul 2015 10:04:07 -0700 Joe Perches <joe@perches.com> wrote:
> 
> > > Le Friday 10 July 2015 __ 04:51 -0700, Joe Perches a __crit :
> > > > On Fri, 2015-07-10 at 13:47 +0200, Jean Delvare wrote:
> > > > > If indent is not found, bail out immediately instead of spitting
> > > > > random shell script error messages.
> > > > 
> > > > OK, but can't we just delete Lindent instead?
> > > 
> > > Because...?
> > 
> > It's just not very useful in today's development space.
> 
> I've very occasionally used Lindent.  It's useful if the input is an
> utter mess.  You feed it through Lindent as a first pass then get in and
> do the remainder by hand.
> 
> It can be less work than doing the whole conversion by hand.

That's true, it can be, but I think Lindent mostly
doesn't work particularly well for reviewing and
it can require a lot more rework.

My biggest complaint about Lindent is that it can
produce _awful_ looking code when it has to wrap
longish lines.

I think that generally, checkpatch --fix-inplace
works better and it can work in discrete steps.

I submitted a little script a while back that does
most of what Lindent does.

https://lkml.org/lkml/2014/7/11/794

uncrustify also kinda works without the line
wrapping nuttiness.  It's not very good about
using Linux's pointer location style.

http://uncrustify.sourceforge.net/

clang-format works reasonably well.
It can respect existing line wrapping.

http://clang.llvm.org/docs/ClangFormatStyleOptions.html



  reply	other threads:[~2015-07-11 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 11:47 [PATCH] Lindent: Handle missing indent gracefully Jean Delvare
2015-07-10 11:51 ` Joe Perches
2015-07-10 13:36   ` Jean Delvare
2015-07-10 17:04     ` Joe Perches
2015-07-10 21:37       ` Andrew Morton
2015-07-11 12:56         ` Joe Perches [this message]
2015-07-15 21:15           ` Jean Delvare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1436619397.2711.19.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox