git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Daode Nurpmeso <sdaoden@googlemail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: Re: [PATCH/RFC] Pro-Git thanks, Control-flow bug report
Date: Mon, 25 Jul 2011 21:39:41 +0200	[thread overview]
Message-ID: <20110725193941.GA95001@sherwood.local> (raw)
In-Reply-To: <20110725162548.GA7071@sigill.intra.peff.net>

@ Jeff King <peff@peff.net> wrote (2011-07-25 18:25+0200):
> Hmm. What's old is new again, I guess. I posted a patch to fix this
> almost exactly 3 years ago:
> 
>   http://article.gmane.org/gmane.comp.version-control.git/90427

Unfortunately your patch from then seems no longer be sufficient
(i.e., from my point of view, say), since this is also coloured:

  ?0%0[steffen@sherwood git.git]$ ./git -c color.ui=auto -c color.pager=false log

>..> It's an ordering problem. [.]
>..> However, breaking the dependency chain would require some pretty
>..> major surgery, I think. [.]
>..> I think the "right" solution would be refactoring the color stuff
>..> to make the decision closer to the point of use. [.]

> A more elegant solution would be to push the query to color.c to
> happen at the time of color use, instead of during the startup
> sequence.

Beginners luck.  In the end git(1) will get a visual.c output
manager, and sideband.c rid of that TERM pollution.  :-)

--Steffen
Ciao, sdaoden(*)(gmail.com)
ASCII ribbon campaign           ( ) More nuclear fission plants
  against HTML e-mail            X    can serve more coloured
    and proprietary attachments / \     and sounding animations

  reply	other threads:[~2011-07-25 19:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 12:50 [PATCH/RFC] Pro-Git thanks, Control-flow bug report Steffen Daode Nurpmeso
2011-07-25 16:25 ` Jeff King
2011-07-25 19:39   ` Steffen Daode Nurpmeso [this message]
2011-07-25 19:49     ` Jeff King

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=20110725193941.GA95001@sherwood.local \
    --to=sdaoden@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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;
as well as URLs for NNTP newsgroup(s).