Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: expl not always local
- X-seq: zsh-workers 21307
- From: Doug Kearns <dougkearns@xxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: PATCH: expl not always local
- Date: Mon, 6 Jun 2005 23:33:06 +1000
- In-reply-to: <1050602152831.ZM12324@xxxxxxxxxxxxxxxxxxxxxxx>
- Mail-followup-to: zsh-workers@xxxxxxxxxx
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20050602132519.GA10266@xxxxxxxxxxxxxxxxxxxxx> <1050602152831.ZM12324@xxxxxxxxxxxxxxxxxxxxxxx>
On Thu, Jun 02, 2005 at 03:28:31PM +0000, Bart Schaefer wrote:
> On Jun 2, 11:25pm, Doug Kearns wrote:
> }
> } Some completion functions aren't declaring expl as local.
>
> } Index: Unix/Type/_file_systems
> } Index: Unix/Type/_global_tags
> } Index: Unix/Type/_locales
> } Index: Unix/Type/_user_at_host
> } Index: X/Type/_x_visual
> } Index: Zsh/Context/_equal
>
> Careful with these. They may be expecting to be called in a context
> where the caller has declared expl as a local.
>
> In general, if a function file starts with #autload then it's a
> utility and should NOT declare completion system variables as locals,
> but if it starts with #compdef then it should declare them local.
> There are probably some exceptions, of course.
These seem to be the only (Type|Context) functions that haven't declared
this local.
Regards,
Doug
Messages sorted by:
Reverse Date,
Date,
Thread,
Author