All of lore.kernel.org
 help / color / mirror / Atom feed
From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] some questions related to output formatting
Date: Thu, 26 Jan 2017 15:18:17 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1701261516370.3109@hadrien> (raw)
In-Reply-To: <FAB49815-C2ED-4463-94A6-A766A21C6F9B@linaro.org>



On Thu, 26 Jan 2017, Kumar Gala wrote:

> 1. Is there a way to adjust the 80 char line break limit?

Currently, it's a non-modifiable configuration variable.  I can add a flag
for it.

> 2. When I?m using a python script that parses a token that crosses multiple lines for some reason the output gets merged onto a single line:
>
> -                       printk(" Min latency from hw interrupt up to 'C' int. "
> -                              "handler:"
> -                              " %d tcs = %d nsec\n",
> +                       printk(" Min latency from hw interrupt up to 'C' int. " "handler:" " %lu tcs = %lu nsec\n?,
>
> Is there something I should be doing special?

I think that it would be difficult to do anything about this.  The string
passes through python and gets modified, and then gets dumped back into
the code in the end.  At that point, Coccinelle just sees it as one atomic
unit.  Does the issue come up a lot?

julia

> I?m using a modified version of Johann?s script for adjusting printf formatters:
>
> https://systeme.lip6.fr/pipermail/cocci/2016-August/003533.html
>
> Thanks
>
> - k
>
>
> _______________________________________________
> Cocci mailing list
> Cocci at systeme.lip6.fr
> https://systeme.lip6.fr/mailman/listinfo/cocci
>

  reply	other threads:[~2017-01-26 14:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 13:45 [Cocci] some questions related to output formatting Kumar Gala
2017-01-26 14:18 ` Julia Lawall [this message]
2017-01-26 14:29   ` Kumar Gala
2017-01-26 15:31     ` Julia Lawall
2017-01-26 15:37     ` Julia Lawall
2017-01-31 10:13       ` Michael Stefaniuc

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=alpine.DEB.2.20.1701261516370.3109@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=cocci@systeme.lip6.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.