From: Ryan Wilkerson <Ryan.Wilkerson@microsoft.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: BUG: Windows Color scheme not preserved
Date: Tue, 10 Nov 2020 20:03:20 +0000 [thread overview]
Message-ID: <MWHPR21MB01435E001D3B779017675B1297E90@MWHPR21MB0143.namprd21.prod.outlook.com> (raw)
In-Reply-To: <MWHPR21MB0143F3E8DA25D35AEB0DB92B97E90@MWHPR21MB0143.namprd21.prod.outlook.com>
Besides the bug below - documentation on 'git bugreport' does not provide any information about where to share the bug report, or explicitly say that it's not submitted (I expected the bug report to be automatically sent).
---
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
I set the color in my Windows cmd-line window to something other than the default. I then ran 'git branch'; from that point forward, text is no longer in the colors specified by the color cmd; instead, it's the default cmdline color scheme.
What did you expect to happen? (Expected behavior)
see above - I expected the specified cmdline color scheme to be preserved
What happened instead? (Actual behavior)
Colors were rolled back to cmd.exe defaults
What's different between what you expected and what actually happened?
Anything else you want to add:
This is a regression - this behavior worked in a build probably 3-4 years ago. I believe it was broken (but unreported) in 2.29.0 or so; it is still not fixed after this upgrade.
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.29.2.windows.2
cpu: x86_64
built from commit: 3464b98ce6803c98bf8fb34390cd150d66e4a0d3
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
uname: Windows 10.0 19042
compiler info: gnuc: 10.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
post-commit
next parent reply other threads:[~2020-11-10 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MWHPR21MB0143F3E8DA25D35AEB0DB92B97E90@MWHPR21MB0143.namprd21.prod.outlook.com>
2020-11-10 20:03 ` Ryan Wilkerson [this message]
2020-11-10 22:42 ` BUG: Windows Color scheme not preserved Johannes Schindelin
2020-11-10 22:45 ` [EXTERNAL] " Ryan Wilkerson
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MWHPR21MB01435E001D3B779017675B1297E90@MWHPR21MB0143.namprd21.prod.outlook.com \
--to=ryan.wilkerson@microsoft.com \
--cc=git@vger.kernel.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 public inbox
https://80x24.org/mirrors/git.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).