Hello,
I have noticed a strange behavior when working with bash "history" command.
Every command in history has its index, and I expected that clearing
history should reset this index to zero. However, running history -c
actually decrements this index by HISTSIZE, so that following commands will
n
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA
On 3/9/18 3:14 AM, don fong wrote:
>
>
> If you'd like to augment the test suite where you feel it lacks something,
> please feel free to do so.
>
>
> tests were included in my patch. you deleted them. i think they should
> be added in.
I understand you're pretty chapped about that.
On 3/10/18 8:27 AM, Janek Warchoł wrote:
> Hello,
>
> I have noticed a strange behavior when working with bash "history" command.
> Every command in history has its index, and I expected that clearing
> history should reset this index to zero. However, running history -c
> actually decrements this
On 3/10/18 9:46 AM, bash...@jonkmans.nl wrote:
> Bash Version: 4.4
> Patch Level: 12
> Release Status: release
>
> Description:
> When a function is ran in a subshell environment (via backticks),
> the program runs faster when that function also writes to stderr.
I don't get these re
