Re: emulate -L sh impact on $0, $argv

[Daniel Shahaf <d.s@daniel.shahaf.name>]

Bart Schaefer wrote on Sun, Jan 31, 2016 at 12:37:45 -0800:
> On Jan 31,  8:13pm, Sebastian Gniazdowski wrote:
> }
> } In sh argv[0] is the same as argv[1]? Because again, you say I
> } shouldn't be able to use argv[0] without KSH_ARRAYS, but in the
> } examples, I do
> 
> This is a side-effect KSH_ARRAYS combined with the behavior of
> $argv / $* / $@ when in the "source" command.  Doc of "." command:
> 
>      If any arguments ARG are given, they become the positional
>      parameters; the old positional parameters are restored when the
>      FILE is done executing.
> 
> What's left unsaid there is that if NO arguments are given, then the
> positional parameters REMAIN THOSE OF THE CALLING CONTEXT.  So argv[0]
> in your example is not test_file.sh's $0, it's the "source" FUNCTION's
> $argv[1].

diff --git a/Doc/Zsh/builtins.yo b/Doc/Zsh/builtins.yo
index 542cecf..5aebdef 100644
--- a/Doc/Zsh/builtins.yo
+++ b/Doc/Zsh/builtins.yo
@@ -81,6 +81,10 @@ then commands are read from that file instead of var(file).
 If any arguments var(arg) are given,
 they become the positional parameters; the old positional
 parameters are restored when the var(file) is done executing.
+However, if no arguments are given,
+the positional parameters remain those of the calling context,
+and no restoring is done.
+
 If var(file) was not found the return status is 127; if var(file) was found
 but contained a syntax error the return status is 126; else the return
 status is the exit status of the last command executed.