all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 5211@emacsbugs.donarmstrong.com
Subject: bug#5211: Color escape codes in the output of vc-git-print-log
Date: Tue, 15 Dec 2009 12:15:42 +0100	[thread overview]
Message-ID: <f7ccd24b0912150315g480d2608x5a842ea454f28395@mail.gmail.com> (raw)
In-Reply-To: <E1NKQ5Z-0007U8-MN@fencepost.gnu.org>

> On what OS?

Windows 7

I have

[color]
        branch = always
        diff = always
        interactive = always
        pager = true
        status = always
        ui = always
        showbranch = always

in my .gitconfig, and

  git log | more

in a personal repo shows

←[33mcommit ed210d6b291c13b3e2c6cbfed39ffd0e96d5b634←[m
Author: Juanma Barranquero <lekktu@gmail.com>
Date:   2009-12-14 18:58:38 +0100

That is not a bug in my setup or git, it's intended to pass color
escapes to less (which I usually use with git).

    Juanma





  reply	other threads:[~2009-12-15 11:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f7ccd24b0912271847j7f282733y358910002b582b49@mail.gmail.com>
2009-12-14 16:12 ` bug#5211: Color escape codes in the output of vc-git-print-log Juanma Barranquero
2009-12-15  4:27   ` Stefan Monnier
2009-12-15  4:31     ` Juanma Barranquero
2009-12-15  5:36       ` Eli Zaretskii
2009-12-15 11:15         ` Juanma Barranquero [this message]
2009-12-15 13:01           ` Eli Zaretskii
2009-12-15 13:09             ` Juanma Barranquero
2009-12-15 14:57   ` Dan Nicolaescu
2009-12-15 15:42     ` Juanma Barranquero
2009-12-15 18:32       ` Andreas Schwab
2009-12-15 18:36         ` Juanma Barranquero
2009-12-15 23:34           ` Andreas Schwab
2009-12-15 23:57             ` Juanma Barranquero
2009-12-28  2:49   ` bug#5211: marked as done (Color escape codes in the output of vc-git-print-log) Emacs bug Tracking System

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=f7ccd24b0912150315g480d2608x5a842ea454f28395@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=5211@emacsbugs.donarmstrong.com \
    --cc=eliz@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.