From: "Nikolay Aleksandrovich Pavlov (ZyX)" <kp-pav@yandex.ru>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: emulate -L sh impact on $0, $argv
Date: Sun, 31 Jan 2016 23:04:10 +0300 [thread overview]
Message-ID: <2970481454270650@web26g.yandex.ru> (raw)
In-Reply-To: <CAKc7PVCWzg0n352x9HSzLm9Q4CxBQVvruUb0YbYt2ERVbmCOwA@mail.gmail.com>
31.01.2016, 22:14, "Sebastian Gniazdowski" <sgniazdowski@gmail.com>:
> On 31 January 2016 at 19:12, Nikolay Aleksandrovich Pavlov (ZyX)
> <kp-pav@yandex.ru> wrote:
>> And in any case has nothing to do with $0, $0 is never present in $argv.
>
> Are you sure? The examples show $0 is in $argv[0]
The example shows `source` in $0. Script name in $argv[0] is *not* $0, it is `source` argument, you may see it in $1 as well.
Best way to examine `$argv` content is
() { emulate -L zsh ; builtin source <(<<< 'printf "<%s>\n" $0 $argv') }
(note: temporary file is not needed, `builtin` is present because my `source` is a function which sets localoptions and noaliases): this will print something like
</proc/self/fd/11>
: in place of printing any arguments it prints only $0.
If I remove `builtin` here, leaving my function
source () {
setopt localoptions
setopt noaliases
builtin source "${@[@]}"
}
(somewhat similar to your function) it will show that when arguments are not empty $1 is the same as $0, and if there are some arguments $1 is first argument given. ***But it is $1.*** Not sure whether or not this is a bug:
() { emulate -L zsh ; source =(<<< 'printf "<%s>\n" $0 $argv') }
</tmp/zshENNMpE>
</tmp/zshENNMpE>
() { emulate -L zsh ; source =(<<< 'printf "<%s>\n" $0 $argv') a b }
</tmp/zshTUoQ9c>
<a>
<b>
. You see: no $0 in $argv in second example (my function for some reason does not work with fds, so I used `=()` and not `<()`).
And note the documentation: it explicitly states that `$argv` is the same thing as `$*` and `$*` is an array containing positional parameters. Even if there *was* `$0` in `$argv` it would be a *bug*.
>
>> Array indexing *may* start with zero, controlled by KSH_ARRAYS
>> option which is again different in zsh and sh emulation mode.
>
> 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
In sh KSH_ARRAYS is set, so indexes are shifted.
>
> Best regards,
> Sebastian Gniazdowski
next prev parent reply other threads:[~2016-01-31 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 18:03 Sebastian Gniazdowski
2016-01-31 18:12 ` Nikolay Aleksandrovich Pavlov (ZyX)
2016-01-31 18:43 ` Bart Schaefer
2016-01-31 19:13 ` Sebastian Gniazdowski
2016-01-31 20:04 ` Nikolay Aleksandrovich Pavlov (ZyX) [this message]
2016-01-31 20:37 ` Bart Schaefer
2016-02-07 0:22 ` Daniel Shahaf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2970481454270650@web26g.yandex.ru \
--to=kp-pav@yandex.ru \
--cc=sgniazdowski@gmail.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).