From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: cannot complete contents of space-containing directories
Date: Mon, 3 Apr 2000 13:07:17 +0200 (MET DST) [thread overview]
Message-ID: <200004031107.NAA31539@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Clint Adams's message of Sun, 2 Apr 2000 11:04:44 -0400
Clint Adams wrote:
> [This is SourceForge Bug #103798]
>
> Something changed between dev-19 and dev-20 wherein directories containing
> spaces will be completed, but any attempts to complete their contents will
> be met with inaction.
Oh, this is ugly. It's a result of 10226: completion in a directory
named `a\#'. There we need the `#' in quoted form, but we don't need
it before the spaces because they are not special to the matching
code.
We could get away with adding a remnulargs() in getarg() if tokenize()
would turn `\ ' into `<Bnull> '. But it doesn't do that.
Hm, committing this to the CVS seems to have worked.
Bye
Sven
Index: Completion/Core/_path_files
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Core/_path_files,v
retrieving revision 1.2
diff -u -r1.2 _path_files
--- Completion/Core/_path_files 2000/04/01 20:43:43 1.2
+++ Completion/Core/_path_files 2000/04/03 10:53:31
@@ -418,9 +418,9 @@
# Next we see if this component is ambiguous.
if [[ "$tmp3" = */* ]]; then
- tmp4=$tmp1[(I)^${(q)tmp1[1]%%/*}/*]
+ tmp4=$tmp1[(I)^${${tmp1[1]%%/*}//(#b)([][\\<>(|)^#~*?])/\\$match[1]}/*]
else
- tmp4=$tmp1[(I)^${(q)tmp1[1]}]
+ tmp4=$tmp1[(I)^${tmp1[1]//(#b)([][\\<>(|)^#~*?])/\\$match[1]}]
fi
if [[ "$tpre" = */* ]]; then
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-04-03 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 11:07 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-02 15:04 Clint Adams
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=200004031107.NAA31539@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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).