zsh-users
 help / color / mirror / code / Atom feed
From: Timothee Cour <timothee.cour2@gmail.com>
To: zsh-users@zsh.org
Subject: tab completion doesn't work if there's a double slash in path
Date: Sat, 31 Dec 2016 17:19:56 -0800	[thread overview]
Message-ID: <CAM4j=kM1AAFf5-KVT-44VSERAVPpzcJka7pFvT_Ae724WKoK=g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 201 bytes --]

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 `//` ?

             reply	other threads:[~2017-01-01  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01  1:19 Timothee Cour [this message]
     [not found] <CAM4j=kM1AAFf5-KVT-44VSERAVPpzcJka7pFvT_Ae724WKoK=g__21261.6231329323$1483233667$gmane$org@mail.gmail.com>
2017-01-01  3:16 ` Daniel Shahaf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM4j=kM1AAFf5-KVT-44VSERAVPpzcJka7pFvT_Ae724WKoK=g@mail.gmail.com' \
    --to=timothee.cour2@gmail.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).