From: <sang.tts.designer@gmail.com>
To: <martin.agren@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: Bug Report with Git Bash
Date: Sun, 19 Mar 2023 20:11:36 +0700 [thread overview]
Message-ID: <002601d95a64$57312bd0$05938370$@gmail.com> (raw)
In-Reply-To: <001d01d95a63$f1fa38b0$d5eeaa10$@gmail.com>
Dear Martin,
What a very quick response!
I just tried your recommendation, and it works.
There is no word that can explain my appreciation, to be honest!
Thanks a million.
--
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: mailto:sang.tts.designer@gmail.com
From: Martin Ågren <mailto:martin.agren@gmail.com>
Sent: Sunday, March 19, 2023 7:28 PM
To: mailto:sang.tts.designer@gmail.com
Cc: mailto:git@vger.kernel.org
Subject: Re: Bug Report with Git Bash
Hi,
On Sunday, 19 March 2023, <mailto:sang.tts.designer@gmail.com> wrote:
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.
This depends on how your shell is configured.
Look into HISTCONTROL and ignoredups.
You might want something like
export HISTCONTROL=ignoredups
in ~/.bashrc.
Martin
next prev parent reply other threads:[~2023-03-19 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 11:35 Bug Report with Git Bash sang.tts.designer
[not found] ` <CAN0heSqEH+AtzXcybPY-Jd-bRtgtKmGrfxbXL-adsvjr_srEZw@mail.gmail.com>
[not found] ` <001d01d95a63$f1fa38b0$d5eeaa10$@gmail.com>
2023-03-19 13:11 ` sang.tts.designer [this message]
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='002601d95a64$57312bd0$05938370$@gmail.com' \
--to=sang.tts.designer@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@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.
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).