Today, a user in the #bash IRC channel of libera.chat, misunderstood how
nullglob is supposed to work because is documented incorrectly in the
man page:
'nullglob'
If set, Bash allows filename patterns which match no files to
expand to a null string, rather than themselves.
On Sun, Nov 05, 2023 at 11:15:50AM +0100, Emanuele Torre wrote:
> Today, a user in the #bash IRC channel of libera.chat, misunderstood how
> nullglob is supposed to work because is documented incorrectly in the
> man page:
>
> 'nullglob'
> If set, Bash allows filename patterns which m
On 11/5/23 5:15 AM, Emanuele Torre wrote:
Today, a user in the #bash IRC channel of libera.chat, misunderstood how
nullglob is supposed to work because is documented incorrectly in the
man page:
'nullglob'
If set, Bash allows filename patterns which match no files to
exp
On 11/6/23 9:22 AM, Andreas Schwab wrote:
On Nov 06 2023, Chet Ramey wrote:
If nullglob is set, the non-matching pattern expands to the null string,
which is removed by word splitting.
Since filename expansion happens after word splitting, this cannot be
true.
Then maybe a better way to put
On Mon, Nov 06, 2023 at 08:56:11AM -0500, Chet Ramey wrote:
> If nullglob is set, the non-matching pattern expands to the null string,
> which is removed by word splitting.
Well, I guess that is one way to look at it, but this explanation does
not make much sense in my opinion since the results of
On Nov 06 2023, Chet Ramey wrote:
> If nullglob is set, the non-matching pattern expands to the null string,
> which is removed by word splitting.
Since filename expansion happens after word splitting, this cannot be
true.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196
On Mon, Nov 06, 2023 at 08:56:11AM -0500, Chet Ramey wrote:
> The null string (NULL) and the empty string ("") are not the same thing.
If this is true, then the man page has many inconsistencies that need
to be cleared up. For example, in the definition of PATH:
PATH The search path for
