zsh-workers
 help / color / mirror / code / Atom feed
From: "Alain Caron" <alainc@nortel.ca>
To: hzoli@vnet.IBM.COM
Cc: coleman@math.gatech.edu, zsh-workers@math.gatech.edu
Subject: Re: zsh not sourcing /etc/profile?
Date: 14 Apr 1997 15:51 EDT	[thread overview]
Message-ID: <199704142054.QAA13764@euclid.skiles.gatech.edu> (raw)

In message "Re: zsh not sourcing /etc/profile?",
'hzoli@vnet.IBM.COM' writes:

>Richard Coleman wrote:
>> I found this article on comp.unix.shells.  I thought I would
>> pass it along.
>[...]
>> > posix-sh, ksh, and bash all return the name of the shell for $0 when
>> > sourcing a file.
>> >
>> > Only zsh returns the name of the file being sourced.  I suspect the
>> > right behaviour is to return the shell name.  The reason for this is
>> > that sourcing a file does not create a new process, it should behave
>> > as if the file had been typed from the keyboard.  If you type the
>> > command "echo $0" at the prompt, it should return the shell name.
>> > Although I really like zsh, I think it does not have the right
>> > behaviour because you can't rely on $0 to determine which shell is
>> > interpreting the file.
>
>Under zsh this is controlled by the FUNCTION_ARGZERO option, which is set
>when zsh is started as sh/ksh.
>
>Zoltan
>

Even there, the behaviour is not the same as ksh.

On HP-UX 9.05


under ksh:

1> echo $0
ksh
2> echo 'echo "$0"' > bar
3> . ./bar
ksh
4> function foo { echo $0 }
5> foo
foo

under zsh :
1> echo $ZSH_VERSION
3.0.2
2> echo $0
zsh
3> [[ -o function_argzero ]] && echo "yes" || echo "no"
yes
4> echo 'echo "$0"' >! bar
5> . ./bar
./bar
6> function foo { echo $0 }
7> foo
foo
8> unsetopt function_argzero
9> [[ -o function_argzero ]] && echo "yes" || echo "no"
no
10> . ./bar
zsh
11> foo
zsh
12> emulate ksh
13> . ./bar
zsh
14> foo
zsh

The behaviour shown by ksh seems, IMHO,  better than the one shown by
zsh.  The reason is that sourcing a file should have the same
behaviour as typing the text.  However, in a function, $0 is more
useful as the name of the function than the name of the shell.

Also, with emulate ksh, the behaviour of zsh is different than ksh.

Shouldn't we change the behaviour of function_argzero option to behave
more like ksh?

Regards,

Alain Caron
Nortel Technology, Montréal, Québec, Canada
email: alainc@nortel.ca


             reply	other threads:[~1997-04-14 21:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-14 19:51 Alain Caron [this message]
1997-04-14 22:38 ` Zoltan T. Hidvegi
     [not found] <5ifr3t$sub@charm.il.ft.hse.nl>
     [not found] ` <risqi5.8t6.ln@sequeira.powernet.co.uk>
     [not found]   ` <5irn2i$b2p@charm.il.ft.hse.nl>
     [not found]     ` <5itdj0$dc0@bmtlh10.bnr.ca>
1997-04-14 17:42       ` Richard Coleman
1997-04-14 18:45         ` Zoltan T. Hidvegi

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=199704142054.QAA13764@euclid.skiles.gatech.edu \
    --to=alainc@nortel.ca \
    --cc=coleman@math.gatech.edu \
    --cc=hzoli@vnet.IBM.COM \
    --cc=zsh-workers@math.gatech.edu \
    /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).