From 1dfc701ec67ecf79e5ee6660d3e573de2577faac Mon Sep 17 00:00:00 2001 From: Fabian Homborg Date: Wed, 27 May 2020 18:11:41 +0200 Subject: [PATCH] docs: Slight rewording on the unmatched globs faq [ci skip] --- doc_src/faq.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc_src/faq.rst b/doc_src/faq.rst index 64b760be7..e11730f87 100644 --- a/doc_src/faq.rst +++ b/doc_src/faq.rst @@ -280,7 +280,7 @@ or appear to work, because most of the time the string doesn't match and so it passes along the `string-*`, which is then interpreted by the receiving program. -But it also causes bash to need workarounds like +But it also means that these commands can stop working at any moment once a matching file is encountered (because it has been created or the command is executed in a different working directory), and for bash to need workarounds like .. code-block:: sh @@ -292,8 +292,6 @@ But it also causes bash to need workarounds like (from http://mywiki.wooledge.org/BashFAQ/004) -And for commands to suddenly stop working once a file with a matching name is created. - For these reasons, fish does not do this, and instead expects asterisks to be quoted or escaped if they aren't supposed to be expanded. This is similar to bash's "failglob" option.