From: "Jan Synáček" <jan.synacek@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 51262@debbugs.gnu.org
Subject: bug#51262: [PATCH] Don't use color escape sequences in `vc-git-expanded-log-entry'
Date: Tue, 19 Oct 2021 10:15:25 +0200 [thread overview]
Message-ID: <CACA+5f2OtJxX++Rmh3Y_e34hKhPrq1a-+Jgzobkm0zMfrhpF2w@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmm9BUBMoboQaqqbC2uGDFRR1UHNKXdqn_3MWGt37kVtBA@mail.gmail.com>
On Tue, Oct 19, 2021 at 7:16 AM Stefan Kangas <stefan@marxist.se> wrote:
> ...
>
> Could you add some details here, such as what problem it is supposed to
> fix? How can I reproduce the issue here, starting from emacs -Q?
Sure. Sorry for not doing it earlier. For some reason, I assumed that this was
obvious.
Here's the reproducer (built from the latest commit on the emacs-28 branch):
1) mkdir /tmp/test
2) cd /tmp/test/
3) git init
4) echo data > file.txt
5) git add file.txt
6) git commit -m "first commit"
7) emacs -Q
8) <run shell and cd /tmp/test>
9) <execute C-x v L>
10) <hit RET on the first commit>
This is what I see on my system (I hope that gmail doesn't remove the escapes):
* (HEAD -> master)520684e..: Jan Synacek 2021-10-19 first commit
^[[33mcommit 520684e773918234874a35738b094ca39b63a822^[ [m
Author: Jan Synacek <jan.synacek@gmail.com>
Date: Tue Oct 19 10:04:02 2021 +0200
first commit
It might be dependent on git configuration, but I think it's safe to assume that
there might be escape sequences and simply use --no-color. And that's what
my patch does.
Regards,
--
Jan Synáček
next prev parent reply other threads:[~2021-10-19 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 10:45 bug#51262: [PATCH] Don't use color escape sequences in `vc-git-expanded-log-entry' Jan Synáček
2021-10-19 5:16 ` Stefan Kangas
2021-10-19 8:15 ` Jan Synáček [this message]
2021-10-19 8:33 ` Stefan Kangas
2021-10-19 8:53 ` Jan Synáček
2021-10-19 18:00 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACA+5f2OtJxX++Rmh3Y_e34hKhPrq1a-+Jgzobkm0zMfrhpF2w@mail.gmail.com \
--to=jan.synacek@gmail.com \
--cc=51262@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).