Re: go through duplicate commands

2019-05-23 Thread Brian Inglis
On 2019-05-23 12:59, A GS wrote: > The option is already in the .bashrc (though commented) of my version. > Neat. Might be the default aswell. $ info bash HISTCONTROL If history is enabled by set -o history, the default action if HISTCONTROL is unset or null, saves all instances of all commands,

Re: go through duplicate commands

2019-05-23 Thread A GS
The option is already in the .bashrc (though commented) of my version. Neat. Might be the default aswell. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.

Re: go through duplicate commands

2019-05-21 Thread Brian Inglis
On 2019-05-21 10:17, Eric Blake wrote: > On 5/21/19 11:10 AM, A GS wrote: >> What about making "up" go through duplicate commands? I think this is the >> behaviour on some linuxes but I don't know the specifics. That would be neat. > > 'info bash HISTCO

Re: go through duplicate commands

2019-05-21 Thread Eric Blake
On 5/21/19 11:10 AM, A GS wrote: > What about making "up" go through duplicate commands? I think this is the > behaviour on some linuxes but I don't know the specifics. That would be neat. 'info bash HISTCONTROL' It sounds like you are asking for the Cygwin /etc/p

go through duplicate commands

2019-05-21 Thread A GS
What about making "up" go through duplicate commands? I think this is the behaviour on some linuxes but I don't know the specifics. That would be neat. ls -a ls ls This would go from ls to ls -a in one (not two) "up"s. -- Problem reports: http://cyg