Thread (3 messages) 3 messages, 2 authors, 2023-03-28

RE: Bug Report with Git Bash

From: Johannes Schindelin <hidden>
Date: 2023-03-27 07:17:38

Hi,

FWIW the reason why you see it in your Ubuntu setup is most likely rooted
in the `/etc/skel/.bashrc` file that contains this:

	# don't put duplicate lines or lines starting with space in the history.
	# See bash(1) for more options
	HISTCONTROL=ignoreboth

Ciao,
Johannes

On Sun, 19 Mar 2023, sang.tts.designer@gmail.com wrote:
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help