Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Allow completion to work with files starting with = (equal sign)
- X-seq: zsh-users 11921
- From: Peter Stephenson <pws@xxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: Allow completion to work with files starting with = (equal sign)
- Date: Wed, 03 Oct 2007 16:27:28 +0100
- In-reply-to: <19c433eb0710030742ya478e23ldb2854ca0e9a4faa@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <19c433eb0710030742ya478e23ldb2854ca0e9a4faa@xxxxxxxxxxxxxx>
"=?ISO-8859-1?Q?Fran=E7ois-Xavier_Coudert?=" wrote:
> Some of my files and directories have names beginning with = (the
> equal sign). By using "unsetopt EQUALS", I can disable the standard
> behaviour for =, and thus am able to use them properly. One thing that
> still doesn't work, though, is the completion of filenames. Typing "cd
> =fo" and TAB doesn't autocomplete to =foo, for example. (Completion
> works fine for me otherwise.) How can I change this behaviour?
This seems to be working fine for me with "compinit" at least as far
back as 4.2.6; it inserts a "\" if there isn't one there, but that's
harmless. Are you using compinit? If you're using the old builtin
completion it's likely to be more haphazard.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
Messages sorted by:
Reverse Date,
Date,
Thread,
Author