On 8/11/20 11:59 AM, Martijn Dekker wrote:
> As I use/try/test many shells, I'm in the habit of using POSIX commands
> such as 'fc -l 1' to list the complete history.
>
> If there have been more than $HISTSIZE command, the list is trimmed at the
> beginning without renumbering, and bash errors out
As I use/try/test many shells, I'm in the habit of using POSIX commands
such as 'fc -l 1' to list the complete history.
If there have been more than $HISTSIZE command, the list is trimmed at
the beginning without renumbering, and bash errors out:
$ fc -l 1
bash-5.0: fc: history specification
Ah, I see the confusion.
The issue you pointed out, "@Q breaks set -o nounset" refers to quote
parameter expansion, as does the line in CHANGES-5.1, 1.q, which makes
sense to call this a bug that was allowed in bash 4.4 and 5.0.
I should have specified, the focus of this issue is the "@a" expansi
On 8/10/20 5:52 PM, Andrew Neff wrote:
> Bash Version: 5.1
> Patch Level: 0
> Release Status: alpha
>
> Description:
> I do not know if this is related to bash 5.1 erroneously being
> "a little aggressive about skipping over empty strings" mentioned
> in "Declaring arrays with empty strin
> > "Can bash please implement multidimensional arrays as I think they're
> > nifty and would like to use them."
> It seems that Chet has never been interested, and no one else has
> stepped up to contribute.
A large reason for this is because bash is a shell, not a programming
language. Another
