Zsh Mailing List Archive
Messages sorted by:
Re: squeeze-slashes false not working?
- X-seq: zsh-workers 29263
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- Subject: Re: squeeze-slashes false not working?
- Date: Fri, 13 May 2011 20:23:15 +0200
- Cc: zsh workers <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=PXZSG6U9z+UQ2Hur1R2NkzT4P81WTKcY6ga24zWFXZQ=; b=ZOfFLK/uAjssPwkHYSXUW4gatVfpvebwGbDe4SkBnFtxsLKZ1onQPnWAC4VqsmQCI/ sKanfcYJRKINBY/Ge733mYNPhWv4CNKDJveaWI0ToggwliYyhBe9eAIqv6ZEUc3t7A83 dgd60cWJrFOZjs1xy96WYb2mcYTkxA8Nmxbd8=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=EZBzLGxz4mVaK3ZFqyF3NIxuhboZajL1mAGHaDx8+BMv2+OFM3pHSSyPu53tt4JDgm BDuuCqrB19+XoUesiQTgqwC3vuriCArb5XXiBbYskFSYTrAqOtrqDG7DjV6rYp48UQOB yzeFQ4STU7XBWim+P8yB4KyuedVlC90hkf+ok=
- In-reply-to: <email@example.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <BANLkTikqnR3pJk8FzRT6Qo9J+wTMGSnycQ@mail.gmail.com> <firstname.lastname@example.org>
On 13 May 2011 20:17, Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx> wrote:
> On Thu, 12 May 2011 19:18:26 +0200
> Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
>> Another old mail:
>> estragib noted on irc that
>> 21:28:58 <estragib> completing ~/d/p/t/i.<TAB> works for
>> ~/dev/prj/test/index.html, as does ~/d/*/*/ind<TAB>. i vaguely remember
>> seeing a setting somewhere that will allow ~/d///ind<TAB> but can't find
>> it again. help? :)
>> and it seems that setting squeeze-slashes to true or false has no
>> effect, the slashes are always squeezed. But it works in zsh -f.
>> But now I can't reproduce it working in zsh -f. At best it jumps back
>> to the first doubleslash and completes at that point. Maybe another
>> option is interfering, any idea which one if so?
> That's the standard feature that it tries to expand path segments before
> the first. It can be turned off by setting the style path-completion to
> false, although what setting it to false does is to allow _path_files to
> skip a prefix of the file that already exists, and I'm not sure what
> happens if there are multiple slashes there.
Hm, with that set, zsh -f starts acting like with my .zshrc, ie as if
I only had one slash. Does ls /////<tab> just show stuff in / for you
too? The documentation for squeeze-slashes says it should act like I
typed ls /*/*/*/*/<tab>.
Messages sorted by: