From: <sang.tts.designer@gmail.com>
To: <git@vger.kernel.org>
Subject: Bug Report with Git Bash
Date: Sun, 19 Mar 2023 18:35:29 +0700 [thread overview]
Message-ID: <000801d95a56$e9253f80$bb6fbe80$@gmail.com> (raw)
Dear Git community,
I have observed a bug related to git bash at my end. Please the following
description.
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)
Please note that 'ls' command just an example, it's happening with any
command.
This is a relatively simple bug. when we double-type a command, like 'ls'.
However, in the Ubuntu environment, the command only occurs once when we
press the top arrow to use the prior command.
It is identical when using git bash.
Repeat these steps:
Type "ls: in git bash.
2. Type "ls" once more.
3. To return to the previous command, use the top arrow.
As you can see, the number of times we type the can command 'ls' does not
matter; it only needs to occur once.
Please be aware that the command "ls" is only an example; this can happen
with any command.
What did you expect to happen? (Expected behavior)
It's only need to appear once time and remove duplicated for more
convenience.
What happened instead? (Actual behavior)
It's depending on how many times we type that command.
What's different between what you expected and what actually happened?
As described above.
Anything else you want to add:
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.33.0.windows.2
cpu: x86_64
built from commit: 8735530946cced809cc6cc4c2ca3b078cdb3dfc8
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 22621
compiler info: gnuc: 10.3
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe
[Enabled Hooks]
--
Thanks and Best Regards!
---------------------------------------------------
Sang Truong Tan
Department of Electronics
HCMC University of Technology
Phone: (+84) 977 600 563 or (+84) 908 983 574
Email: sang.tts.designer@gmail.com
next reply other threads:[~2023-03-19 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 11:35 sang.tts.designer [this message]
[not found] ` <CAN0heSqEH+AtzXcybPY-Jd-bRtgtKmGrfxbXL-adsvjr_srEZw@mail.gmail.com>
[not found] ` <001d01d95a63$f1fa38b0$d5eeaa10$@gmail.com>
2023-03-19 13:11 ` Bug Report with Git Bash sang.tts.designer
2023-03-27 7:17 ` Johannes Schindelin
2023-03-28 13:16 ` sang.tts.designer
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='000801d95a56$e9253f80$bb6fbe80$@gmail.com' \
--to=sang.tts.designer@gmail.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).