diff options
author | Ron Yorston <rmy@pobox.com> | 2020-06-14 10:17:04 +0100 |
---|---|---|
committer | Ron Yorston <rmy@pobox.com> | 2020-06-14 10:17:04 +0100 |
commit | f41697493de1a25d0f56930d81cf9560172ce7b7 (patch) | |
tree | 998b60552725808730478c3288f2452a40ffe7b8 /docs | |
parent | b1a5034ca852efe2c24212db77d7b0b2660a687b (diff) | |
download | busybox-w32-f41697493de1a25d0f56930d81cf9560172ce7b7.tar.gz busybox-w32-f41697493de1a25d0f56930d81cf9560172ce7b7.tar.bz2 busybox-w32-f41697493de1a25d0f56930d81cf9560172ce7b7.zip |
win32: enable globbing by default
Change how busybox.exe expands wildcards on the command line.
When globbing is enabled at compile time provide an implementation
of _setargv(), which is run early during startup of C programs. This:
- enables globbing by setting _dowildcard to -1
- checks for the presence of the environment BB_GLOBBING
- if it exists and is set to 0 disables globbing
- if it doesn't exist sets BB_GLOBBING=0 but continues to apply
Windows' globbing in the current process
The consequences of this are:
- When busybox.exe is initially run from a Command Prompt Windows'
globbing is applied;
- Windows' globbing is turned off for future child processes, thus
allowing the shell re-execute busybox.exe without it interfering
with wildcards;
- this behaviour can be overridden by setting BB_GLOBBING explicitly.
Globbing can still be disabled at compile time if required. In that
case BB_GLOBBING has no effect.
With these changes globbing can be enabled by default and BusyBox
will do the right thing in most circumstances.
(See GitHub issues #172 and #189.)
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions