Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: ${path[@]} in sh mode [was: Segfault with zsh 5.2]
- X-seq: zsh-workers 37732
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: Martijn Dekker <martijn@xxxxxxxx>
- Subject: Re: ${path[@]} in sh mode [was: Segfault with zsh 5.2]
- Date: Sat, 23 Jan 2016 01:07:41 +0100
- Cc: Peter Stephenson <p.stephenson@xxxxxxxxxxx>, zsh workers <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iuRjdbwvQzwq7Z5xWjhc4f4p6hjb1f3j/QTqsZMw9M0=; b=MxYlUpYcAZhVSUC9C+w8I+RIhd3agejcOAf2+dmVh2YQvssv4M1xJQS9+gXipiNowJ HNUc8PlCCfkYkcInLduRvZPhLz3u38iqRG0mMobxUwzgPMjavPSjXJa7IFN/Y1frsMZ0 snfQRuGRxu4MFMZagNunAlcocbgKFLblBZojfOcLT13ojrzAsQ+Y6ON5C/dvfSPd0Ju1 U/x1cGw0NcO1N8rI0Psvnj9omERCOJH4XtHjAVC6KpldZCAPgYeLcFa8iaGVU/HFVjmx OAjC8LHF/bLimbf+2GrkTOa3sUX1PEolLgo8d5Vwm5MDqTYB+LY/wLyeDDY8uFuanNxR lI3g==
- In-reply-to: <56A294F9.5020509@inlv.org>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <87h9jujttm.fsf@gmail.com> <20151207135532.1a285c15@pwslap01u.europe.root.pri> <878u56jpob.fsf@gmail.com> <20151207143621.3cbbe7bd@pwslap01u.europe.root.pri> <56A28D28.3090701@inlv.org> <56A294F9.5020509@inlv.org>
On Fri, Jan 22, 2016 at 9:45 PM, Martijn Dekker <martijn@xxxxxxxx> wrote:
> Martijn Dekker schreef op 22-01-16 om 20:12:
>> Peter Stephenson schreef op 07-12-15 om 14:36:
>>> Change now pushed.
>>
>> Can the ${path[@]} array be disabled in sh mode? I just noticed that it
>> auto-syncs with the system $PATH. Lowercase "path" is a perfectly normal
>> variable name in other shells and is a common English word, so conflicts
>> that result in corruption of $PATH are not unlikely when running scripts
>> written using other shells.
>
> Never mind: it is disabled when zsh is launched as sh (but not when
> launched as zsh and then executing 'emulate sh'). So I suppose it was
> decided long before that disabling it post-launch is not feasible. Sorry
> for the noise.
If you're in a function context, you can say 'typeset -h path' to hide
the specialness of $path and declare a new local of the same name. Eg,
one that isn't connected to PATH.
--
Mikael Magnusson
Messages sorted by:
Reverse Date,
Date,
Thread,
Author