From: Oliver Kiddle <opk@u.genie.co.uk>
To: zsh-workers@sunsite.dk
Subject: Re: Another keep-prefix problem
Date: Thu, 26 Apr 2001 15:27:32 +0100 [thread overview]
Message-ID: <3AE83054.3BE06044@u.genie.co.uk> (raw)
Sven Wischnowsky wrote:
> I won't commit this before I get positive replies and answers to the
> question if we then should add another possible value for the
> keep-prefix style for this new behaviour or if that's not needed (I
As seems to be the consensus, I don't think we need another value for
keep-prefix for this.
This is more than likely nothing to do with the latest patch but when
I tried testing all this, things didn't work as I'd like or expect.
For _expand I use the glob 1, substitute 1, suffix 1, accept-exact
false and tag-order all-expansions styles. keep-prefix changed is
the default so that too.
To test I did:
c1=/home
c3=cvs
Now,
cd $c1/kiddleo/$c3/<tab> expands both $c1 and $c3 which I don't want.
Having typed the / after $c3, I expect it to complete subdirectories
in my ~/cvs and not do expansion.
Okay, so I tried setting keep-prefix to 1 and things start working nicely.
Except what is going on here (where I mix globs with variables):
cd /home/kiddle?/$c3/<tab> results in:
cd /home/kiddle?/$c3//home/kiddleo/cvs/
this definitely isn't right.
So in what situations is the changed value of keep-prefix useful for?
It sounds something like subst-globs-only from the docs. I can't
remember why I used it and not a value of 1.
Actually, talking of the docs for styles, the section on tag-order is
messed up and seems to have the same example twice.
Oliver
next reply other threads:[~2001-04-26 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 14:27 Oliver Kiddle [this message]
2001-04-26 15:43 ` Wayne Davison
2001-04-26 17:18 ` Bart Schaefer
2001-04-26 23:38 ` Wayne Davison
2001-04-27 9:03 ` Sven Wischnowsky
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 0:46 Wayne Davison
2001-04-24 16:50 ` Bart Schaefer
2001-04-24 19:18 ` Wayne Davison
2001-04-25 13:25 ` Sven Wischnowsky
2001-04-26 4:33 ` Bart Schaefer
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=3AE83054.3BE06044@u.genie.co.uk \
--to=opk@u.genie.co.uk \
--cc=zsh-workers@sunsite.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).