Reinstate failglob behaviour for most commands

Expand globs to zero arguments (nullglob) only for set, for and count.

The warning about failing globs, and setting the accompanying $status,
now happens regardless of mode, interactive or not.

It is assumed that the above commands are the common cases where
nullglob behaviour is desirable.
More importantly, doing this with `set` is a real feature enabler,
since the resulting empty array can be passed on to any command.

The previous behaviour was actually all nullglob (since commit
cab115c8b9933ae7db9412c66d452c0ccb2d7152), but this was undocumented;
the failglob warning was still printed in interactive mode,
and the documentation was bragging about failglob behaviour.

1 files changed, 3 insertions, 0 deletions

diff --git a/tests/test5.err b/tests/test5.err
index e69de29b..7dba999c 100644
--- a/tests/test5.err
+++ b/tests/test5.err
@@ -0,0 +1,3 @@
+No matches for wildcard '*ee*'.
+fish: 	case *ee*
+      	     ^