From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@cambridgesiliconradio.com>,
zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: completing directory path
Date: Sat, 8 Jul 2000 06:06:52 +0000 [thread overview]
Message-ID: <1000708060653.ZM2459@candle.brasslantern.com> (raw)
In-Reply-To: <1000707193233.ZM1522@candle.brasslantern.com>
On Jul 7, 7:32pm, Bart Schaefer wrote:
}
} On Jul 7, 7:16pm, Peter Stephenson wrote:
} }
} } > On Jul 7, 5:12pm, Peter Stephenson wrote:
} } > }
} } > } completion has stopped working on ~1/... etc.
} } >
} } > What are your styles? This works for me. Well, it sort of works; I first
} } > get ~1/ --> ~+1/ and then completion after ~+1/ works as expected.
} }
} } I can reproduce it with completely vanilla new completion, but it's weirder
}
} However, *I'm* now getting some inconsistent behavior, because it's not
} replacing ~1 with ~+1 which it definitely was before.
Ahem. It helps to have run compinit in order to see the new completion
behavior.
With compinit -D, I get:
zagzig% autoload -U compinit; compinit -D
zagzig% pushd /tmp
/tmp ~
zagzig% cd ~1/i<TAB>
(feep)
TAB or C-d doesn't matter, I just get feep.
However:
zagzig% cd ~1/<TAB>
zagzig% cd ~+1/
Thereafter, completion works normally:
zagzig% cd ~+1/i<TAB>
zagzig% cd ~+1/images/
So I still can't reproduce what PWS reported (the "command not found" at
line 153 of _main_complete). So this question stands:
} Does it perhaps have something more to do with the contents of directories
} in the dirstack than just whether there is a unique match for one of the
} files?
However, looking at C-x? output, there appears to be a problem at line 560
of _path_files. There's a call to compadd like this:
+_path_files:559> compquote tmp4 tmp1
+_path_files:560> compadd -Qf -J -default- -p ~+1/ -W /home/schaefer/ -M r:|/=* r:|=* -a tmp1
Note the `-p ~+1/' -- the actual string from the line is ~1, so that compadd
fails to add anything even though $tmp1 has the correct value ("images").
This has ultimately come from line 214, which sticks the `+' into $linepath.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-07-08 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 16:12 Peter Stephenson
2000-07-07 17:07 ` Bart Schaefer
2000-07-07 18:16 ` Peter Stephenson
2000-07-07 19:32 ` Bart Schaefer
2000-07-08 6:06 ` Bart Schaefer [this message]
2000-07-08 22:21 ` Peter Stephenson
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=1000708060653.ZM2459@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=pws@cambridgesiliconradio.com \
--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).