Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: tab completion doesn't work if there's a double slash in path
- X-seq: zsh-users 22313
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: Timothee Cour <timothee.cour2@xxxxxxxxx>
- Subject: Re: tab completion doesn't work if there's a double slash in path
- Date: Sun, 1 Jan 2017 03:16:09 +0000
- Cc: zsh-users@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= mesmtp; bh=uayHWxwS4jcercPpBCyMV1Qdq1s=; b=nqW8FyeugzrBuVX+giKeT +jOM9XTs/NR4wETfmM7MI0xyqT0R3aOJjuuan3z6C14hX2L73ieExt6ZcaafDokh MdETOG/ZJysptCZnrO6o3v/c86nsFyLSluXCA56DG7I61IDXVmi4CJmuV+4disPj vkeEgFoj9P/0LYott4Tnkw=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=uayHWxwS4jcercPpBCyMV1Qdq1s=; b=l0Xh7Vks7DhXJg0amAaL G1kmtX103LfV/TbgTIbzZAxE0PBzVHIqjhQvU0ZA7U2k7fs7k4qDBuBN8RtXtEMx Kbig60KOjW0hacwcp/m/u0/UsXBODI6c1bLBH8geG14K53GBkRK82lF8ikHisWJ4 UVF7wD4xl0BwhlCcI3S07Mg=
- In-reply-to: <CAM4j=kM1AAFf5-KVT-44VSERAVPpzcJka7pFvT_Ae724WKoK=g__21261.6231329323$1483233667$gmane$org@mail.gmail.com>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <CAM4j=kM1AAFf5-KVT-44VSERAVPpzcJka7pFvT_Ae724WKoK=g__21261.6231329323$1483233667$gmane$org@mail.gmail.com>
Timothee Cour wrote on Sat, Dec 31, 2016 at 17:19:56 -0800:
> ls /Users/foo/bar//fob1/fob[TAB] doesn't auto-complete because there is a
> double slash (//) somewhere in the path.
> This case often happens in my workflow. Could autocomplete work in presence
> of `//` ?
It's not a bug, it's a feature: with two consecutive slashes, it looks
for paths of the form /Users*/foo*/bar*/*/fob1*/fob*.
* danielsh greps zshcompsys(1)…
There's a 'squeeze-slashes' style you can set to disable that:
zstyle :completion:\* squeeze-slashes true
Cheers,
Daniel
Messages sorted by:
Reverse Date,
Date,
Thread,
Author