Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: expl not always local
- X-seq: zsh-workers 21303
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Doug Kearns <dougkearns@xxxxxxxxx>, zsh-workers@xxxxxxxxxx
- Subject: Re: PATCH: expl not always local
- Date: Thu, 02 Jun 2005 15:28:31 +0000
- In-reply-to: <20050602132519.GA10266@xxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20050602132519.GA10266@xxxxxxxxxxxxxxxxxxxxx>
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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author