From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: Recursive Completition
Date: Mon, 20 Aug 2012 21:58:19 -0700 [thread overview]
Message-ID: <120820215819.ZM13320@torch.brasslantern.com> (raw)
In-Reply-To: =?iso-8859-1?Q?=3C503206C8=2E5050408=40necoro=2Eeu=3E?= =?iso-8859-1?Q?Comments=3A_In_reply_to_Ren=E9_Neumann_=3Clists=40necoro?= =?iso-8859-1?Q?=2Eeu=3E?= =?iso-8859-1?Q?________=22Re=3A_Recursive_Completition=22_=28Aug_20=2C_11?= =?iso-8859-1?Q?=3A43am=29?=
On Aug 20, 11:43am, René Neumann wrote:
} Subject: Re: Recursive Completition
}
} Am 19.08.2012 02:18, schrieb Bart Schaefer:
} > setopt globcomplete
} >
} > Now when you try
} >
} > ls **/Kern[tab]
} >
} > the completion system behaves as if you'd inserted a * just before [tab],
} > and offers you the list of matching items as choices.
}
} Really? I tried this, and noticed you still have to enter the * before
} the [tab].
Hmm, interesting. I didn't try it for a sufficiently deep directory
hierarchy. Completion seems to treat **/ as just */ -- only expansion
does the full recursive thing.
Looking more closely, completion splits **/Kern into "**" and "Kern" and
tries to find completions for ** first. Because the slash has been
removed, ** loses its special meaning.
So it really does need somethng like PWS's recent proposed patch. Or else
further surgery to _path_files, which is already a bit of a Frankenstein's
monster.
prev parent reply other threads:[~2012-08-21 4:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 21:09 Karoly Negyesi
2012-08-19 0:18 ` Bart Schaefer
2012-08-19 19:44 ` Peter Stephenson
2012-08-19 21:07 ` Karoly Negyesi
2012-08-20 8:57 ` Peter Stephenson
2012-08-20 15:33 ` Bart Schaefer
2012-08-21 18:27 ` Peter Stephenson
2012-12-04 2:13 ` Karoly Negyesi
2012-08-20 9:43 ` René Neumann
2012-08-21 4:58 ` Bart Schaefer [this message]
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=120820215819.ZM13320@torch.brasslantern.com \
--to=schaefer@brasslantern.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).