emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

ash: explain EXP_REDIR and why we (dont) glob redir filenames

Browse Source 
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
Denys Vlasenko 2016-10-24 21:12:33 +02:00
parent 61d5997b58
commit db74c6caed
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
shell/ash.c
View File

@ -5545,6 +5545,17 @@ ash_arith(const char *s)
#define EXP_TILDE 0x2 /* do normal tilde expansion */
#define EXP_VARTILDE 0x4 /* expand tildes in an assignment */
#define EXP_REDIR 0x8 /* file glob for a redirection (1 match only) */
/* ^^^^^^^^^^^^^^ this is meant to support constructs such as "cmd >file*.txt"
* POSIX says for this case:
* Pathname expansion shall not be performed on the word by a
* non-interactive shell; an interactive shell may perform it, but shall
* do so only when the expansion would result in one word.
* Currently, our code complies to the above rule by never globbing
* redirection filenames.
* Bash performs globbing, unless it is non-interactive and in POSIX mode.
* (this means that on a typical Linux distro, bash almost always
* performs globbing, and thus diverges from what we do).
*/
#define EXP_CASE 0x10 /* keeps quotes around for CASE pattern */
#define EXP_QPAT 0x20 /* pattern in quoted parameter expansion */
#define EXP_VARTILDE2 0x40 /* expand tildes after colons only */