bash history for each folder it was ran in.

.bash_history for each folder perhaps in one large sql database. and a nice gui to run it and clear it maybe a weekly option for the cautious.

Issue – Invalid command documented – BASH_BUILTINS(1) –

OS: Fedora; Component: bash.x86_64 4.4.23-1.fc28 @updates Description: Non-valid documented command 'BASH_BUILTINS(1)'. $ man 1 bash_builtins No manual entry for bash_builtins in section 1 $ man bash_builtins No manual entry for bash_builtins Additional informations: $ apropos bash (...) alias (

Re: Issue – Invalid command documented – BASH_BUILTINS(1) –

On 7/14/18 10:38 AM, Ricky Tigg wrote: > OS: Fedora; Component: bash.x86_64 4.4.23-1.fc28 @updates > > Description: Non-valid documented command 'BASH_BUILTINS(1)'. This is an issue to take up with Fedora. But doesn't this show that the `command' isn't `documented': > $ man 1 bash_builtins > No

Re: Issue – Invalid command documented – BASH_BUILTINS(1) –

On 07/14/2018 09:38 PM, Ricky Tigg wrote: > $ man 1 bash_builtins The variable is BASH_BUILTINS but the man page is bash-builtins (underscore vs. dash). Peter

Re: Issue – Invalid command documented – BASH_BUILTINS(1) –

That's what I indeed observed; since 'BASH_BUILTINS(1)' is documented here written in the conventional syntax; then at least it tends to indicate that its respective command 'man 1 bash_builtins' can be executed in Bash. Maybe then there is an hidden reason for which it should be considered accordi

${parameter@A} doesn't work should no value be set

Configuration Information: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYP$ uname output: Linux pish-lub 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_6$ Machine Type: x86_