git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Preston, David J." <David.Preston@onegas.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git bash bug
Date: Wed, 9 Jul 2025 22:47:09 +0000	[thread overview]
Message-ID: <aG7xbbPf2ZsTh1ND@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <PH7PR11MB65466DEE20BA470C600C7B9B9549A@PH7PR11MB6546.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]

On 2025-07-09 at 17:20:22, Preston, David J. wrote:

Hi,

> 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)
> started happening after an update to a newer version of git... has been happening for a while, so i am not sure what version it started with
> 
> What did you expect to happen? (Expected behavior)
> when using git bash in windows environment, when a previously typed command is executing and i start typing, i expect that what i type will eventually show up on the command line, in the order i typed it, once the executing command completes.

The Git project doesn't ship bash, a terminal, or any software other
than the source code to Git.  Git Bash is part of Git for Windows, which
is a separate project.  You may want to report this https://github.com/git-for-windows/git/issues.

I would recommend searching for any relevant issues, open or closed,
first and providing any information that might be relevant.  For
instance, does this problem only occur when the system is loaded or does
it happen all the time, even with little load?  Is there anything else
going on that is correlated with the problem (e.g., a virus scan)?  Does
the same thing happen when running Git for Windows's bash through
Windows Terminal, or is it only the built-in MinTTY?  Those kinds of
things might help the maintainer solve the problem more quickly.

Best of luck on this.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2025-07-09 22:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09 17:20 git bash bug Preston, David J.
2025-07-09 22:47 ` brian m. carlson [this message]
2025-07-11 14:40 ` Johannes Schindelin
  -- strict thread matches above, loose matches on Subject: below --
2017-07-14 13:43 Git Bash Bug Kavita Desai
2017-07-14 14:28 ` Johannes Schindelin
2017-07-14 14:34   ` Kavita Desai
2017-07-14 14:37     ` Paul Smith
2017-07-14 14:59       ` Kavita Desai
2017-07-14 15:03         ` Paul Smith
2017-07-14 20:33           ` Johannes Schindelin
2017-07-14 21:12             ` Paul Smith
2017-07-14 21:52               ` Johannes Schindelin

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=aG7xbbPf2ZsTh1ND@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=David.Preston@onegas.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.
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).