git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Simon Courtois <scourtois@cubyx.fr>
Cc: git@vger.kernel.org
Subject: [PATCH 0/2] more ANSI attributes
Date: Thu, 23 Jun 2016 09:08:29 -0400	[thread overview]
Message-ID: <20160623130828.GA25209@sigill.intra.peff.net> (raw)
In-Reply-To: <etPan.576bcdfa.7aee6fa4.9bf5@cubyx.fr>

On Thu, Jun 23, 2016 at 01:54:34PM +0200, Simon Courtois wrote:

> I was looking for a way to use italics in my git log. I ended-up
> looking at the code dealing with colors and style and noticed that the
> italic code was skipped when defining the list (color.c:128 if I'm not
> mistaken).
> 
> I'd love to propose a contribution but I'm sadly not very well versed
> with C.

My first suggestion was going to be that you can feed arbitrary numbers
yourself, without git having to have a name for it. But that is true
only of colors, not attributes. So it does need a patch.

Here is one, along with a minor cleanup. I think the attributes we don't
support now are:

  - 6; rapid blink (not supported by xterm)
  - 8; conceal (supported, but why would you want it?)
  - 9; crossed-out (supported, and at least plausible to want?)

We also don't support font-selection (10-19, or 20 for Fraktur) which
are not supported by xterm (of course xterm support is not the defining
criterion, if people have other terms that do support it. My point is
mostly "nobody is asking for it, and it is not even in xterm").

  [1/2]: color: fix max-size comment
  [2/2]: color: support "italic" attribute

-Peff

  reply	other threads:[~2016-06-23 13:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 11:54 Italics formatting Simon Courtois
2016-06-23 13:08 ` Jeff King [this message]
2016-06-23 13:09   ` [PATCH 1/2] color: fix max-size comment Jeff King
2016-06-23 13:10   ` [PATCH 2/2] color: support "italic" attribute Jeff King
2016-06-23 13:57     ` Simon Courtois
2016-06-23 16:46     ` Junio C Hamano
2016-06-23 16:47       ` Jeff King
2016-06-23 17:30   ` [PATCH v2 0/7] more ANSI attributes Jeff King
2016-06-23 17:31     ` [PATCH v2 1/7] color: fix max-size comment Jeff King
2016-06-23 17:32     ` [PATCH v2 2/7] doc: refactor description of color format Jeff King
2016-06-23 17:33     ` [PATCH v2 3/7] add skip_prefix_mem helper Jeff King
2016-06-23 17:38     ` [PATCH v2 4/7] color: refactor parse_attr Jeff King
2016-06-23 17:38     ` [PATCH v2 5/7] color: allow "no-" for negating attributes Jeff King
2016-06-23 17:39     ` [PATCH v2 6/7] color: support "italic" attribute Jeff King
2016-06-23 18:34       ` Junio C Hamano
2016-06-23 18:36         ` Jeff King
2016-06-23 17:40     ` [PATCH v2 7/7] color: support strike-through attribute Jeff King
2016-06-23 18:36       ` Junio C Hamano
2016-06-23 18:39         ` Jeff King
2016-06-23 18:52           ` Junio C Hamano
2016-06-23 19:03             ` Junio C Hamano
2016-06-23 19:04             ` Jeff King
2016-06-23 19:11               ` Junio C Hamano
2016-06-23 19:56           ` Junio C Hamano

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=20160623130828.GA25209@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=scourtois@cubyx.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 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).