all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: guix lint
Date: Thu, 07 Apr 2016 23:48:51 +0200	[thread overview]
Message-ID: <8760vt84zg.fsf@gnu.org> (raw)
In-Reply-To: <20160407150957.GA18750@jasmine> (Leo Famulari's message of "Thu, 7 Apr 2016 11:09:57 -0400")

Leo Famulari <leo@famulari.name> skribis:

> On Thu, Apr 07, 2016 at 02:37:44PM +0200, Danny Milosavljevic wrote:
>> Currently, when run from gnome-terminal, "guix lint" prints CR and then writes a shorter text, resulting in a less-than-ideal display.
>> 
>> I propose to clear-to-end-of-line before that.
>> 
>> Also, at the very end of the lint check it still did this:
>> 
>> dannym@dayas ~/src/guix$ -0.9.4 [formatting]...
>> 
>>                          ^^^^
>> 
>> Therefore, I clear the line at the very end of "run-checkers" as well.
>
> It works, thank you! This has been on my 'to-do list' for a while.

Same here.  :-)

There may other places to fix, see <http://bugs.gnu.org/22536>.

> Does anyone else have any comments?

Not me!

Thanks!

Ludo’.

  parent reply	other threads:[~2016-04-07 21:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 12:37 guix lint Danny Milosavljevic
2016-04-07 15:09 ` Leo Famulari
2016-04-07 17:20   ` Efraim Flashner
2016-04-07 21:48   ` Ludovic Courtès [this message]
2016-04-08 18:07     ` bug#22536: " Danny Milosavljevic
2016-04-08 18:07     ` Danny Milosavljevic
2016-04-08 18:45       ` bug#22536: Progress on the guix download progress display Danny Milosavljevic
2016-04-14 22:38       ` bug#22536: guix lint Ludovic Courtès
2016-04-14 22:38       ` Ludovic Courtès
2016-04-08 15:59 ` [PATCH] guix lint: at the "checking" line, make sure to delete the old line's text before overwriting it (with a possibly shorter text) Danny Milosavljevic
2016-04-13 21:20   ` Ludovic Courtès

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=8760vt84zg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.