bug#46023: No error when a qualified eshell glob fails to match

[Jim Porter]

On 1/21/2021 10:03 AM, ch.emacs@themaw.xyz wrote:
> With eshell-error-if-no-glob set to t, eshell will give en error when a 
> glob fails to match, e.g. `ls *` in an empty directory. However, if a 
> qualified glob fails to match, the behaviour is inconsistent, depending 
> on whether the lack of matches is due to the glob or the qualifier. For 
> example `ls *(@)` in an empty directory will error (* does not match), 
> but `ls *(@)` in a directory with no symlinks will not ((@) does not 
> match).

I fixed this in commit 598d7c5d1c10bfb161cb53aa76d480864414487c. (It was 
listed as a TODO entry in the Eshell manual.)

Closing this now. If there's something I missed when fixing this, feel 
free to reply to the bug and I'll take another look.