From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 5211@emacsbugs.donarmstrong.com
Subject: bug#5211: Color escape codes in the output of vc-git-print-log
Date: Tue, 15 Dec 2009 08:01:36 -0500 [thread overview]
Message-ID: <E1NKX20-0003aZ-0N@fencepost.gnu.org> (raw)
In-Reply-To: <f7ccd24b0912150315g480d2608x5a842ea454f28395@mail.gmail.com> (message from Juanma Barranquero on Tue, 15 Dec 2009 12:15:42 +0100)
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Tue, 15 Dec 2009 12:15:42 +0100
> Cc: 5211@emacsbugs.donarmstrong.com, monnier@iro.umontreal.ca
>
> > On what OS?
>
> Windows 7
I asked because pipes on Windows have their quirks.
> 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
If the escapes go away when you remove "always", then there's no
problem here. And if we want to cater to users who set "always" like
you do, then resetting it in vc-git-print-log is IMO the way to go.
next prev parent reply other threads:[~2009-12-15 13:01 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
2009-12-15 13:01 ` Eli Zaretskii [this message]
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=E1NKX20-0003aZ-0N@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=5211@emacsbugs.donarmstrong.com \
--cc=lekktu@gmail.com \
/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.