Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: completion with midword tildes
- X-seq: zsh-workers 9300
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: completion with midword tildes
- Date: Wed, 12 Jan 2000 16:49:27 +0000
- In-reply-to: <200001120907.KAA31890@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <200001120907.KAA31890@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Jan 12, 10:07am, Sven Wischnowsky wrote:
} Subject: Re: completion with midword tildes
}
} A pure user-code solution would be to use a match spec such as 'm:=\\'
} (or several of these, making the backslash only optional before some
} special characters) in ones $compmatchers, but maybe we should make
} the completion code do that by default. What I want to say is that
} nowadays I would implement it in exactly this way -- modify the
} matching function to ignore backslashes. That's what the patch below
} tries to attempt -- it works but there may be some complicated
} interactions with complex match specs, I'll have to test that.
What happens if the file name (or whatever else is being completed)
actually *contains* a backslash? I.e. the backslash isn't just there
to quote some other special character.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author