* completing directory path
@ 2000-07-07 16:12 Peter Stephenson
2000-07-07 17:07 ` Bart Schaefer
0 siblings, 1 reply; 6+ messages in thread
From: Peter Stephenson @ 2000-07-07 16:12 UTC (permalink / raw)
To: Zsh hackers list
completion has stopped working on ~1/... etc.
% pushd ~1/^D
works OK but
% pushd ~1/D^D_main_complete:153: command not found: 1
_main_complete:153: command not found: 1
Completing `directory' or `corrections'
--
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: completing directory path
2000-07-07 16:12 completing directory path Peter Stephenson
@ 2000-07-07 17:07 ` Bart Schaefer
2000-07-07 18:16 ` Peter Stephenson
0 siblings, 1 reply; 6+ messages in thread
From: Bart Schaefer @ 2000-07-07 17:07 UTC (permalink / raw)
To: Peter Stephenson, Zsh hackers list
On Jul 7, 5:12pm, Peter Stephenson wrote:
} Subject: completing directory path
}
} 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.
This problem was reported at least once before by somebody else, but the
mailing list archive is not responding right now so I can't look it up.
--
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: completing directory path
2000-07-07 17:07 ` Bart Schaefer
@ 2000-07-07 18:16 ` Peter Stephenson
2000-07-07 19:32 ` Bart Schaefer
0 siblings, 1 reply; 6+ messages in thread
From: Peter Stephenson @ 2000-07-07 18:16 UTC (permalink / raw)
To: Zsh hackers list
> On Jul 7, 5:12pm, Peter Stephenson wrote:
> } Subject: completing directory path
> }
> } 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
than I said: it only happens when there is a unique match for the file in
question (which may explain why I needed to type the first character).
This seems to be completely reproducible and as far as I can see not style
dependent. It may be related to the fact that the `+' doesn't get inserted
in this case.
--
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: completing directory path
2000-07-07 18:16 ` Peter Stephenson
@ 2000-07-07 19:32 ` Bart Schaefer
2000-07-08 6:06 ` Bart Schaefer
0 siblings, 1 reply; 6+ messages in thread
From: Bart Schaefer @ 2000-07-07 19:32 UTC (permalink / raw)
To: Peter Stephenson, Zsh hackers list
On Jul 7, 7:16pm, Peter Stephenson wrote:
} Subject: Re: completing directory path
}
} > On Jul 7, 5:12pm, Peter Stephenson wrote:
} > } Subject: completing directory path
} > }
} > } 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
} than I said: it only happens when there is a unique match for the file in
} question (which may explain why I needed to type the first character).
zagzig[131] zsh -f
zagzig% echo $ZSH_VERSION
3.1.9-dev-2
zagzig% dirs
~
zagzig% echo i*
images
zagzig% pushd /tmp
/tmp ~
zagzig% cd ~1/i<TAB>
zagzig% cd ~1/images/
zagzig% cd ~1/i<C-d>
zagzig% cd ~1/i
images/
} This seems to be completely reproducible and as far as I can see not style
} dependent. It may be related to the fact that the `+' doesn't get inserted
} in this case.
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, *I'm* now getting some inconsistent behavior, because it's not
replacing ~1 with ~+1 which it definitely was before.
--
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: completing directory path
2000-07-07 19:32 ` Bart Schaefer
@ 2000-07-08 6:06 ` Bart Schaefer
2000-07-08 22:21 ` Peter Stephenson
0 siblings, 1 reply; 6+ messages in thread
From: Bart Schaefer @ 2000-07-08 6:06 UTC (permalink / raw)
To: Peter Stephenson, Zsh hackers list
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: completing directory path
2000-07-08 6:06 ` Bart Schaefer
@ 2000-07-08 22:21 ` Peter Stephenson
0 siblings, 0 replies; 6+ messages in thread
From: Peter Stephenson @ 2000-07-08 22:21 UTC (permalink / raw)
To: Zsh hackers list
"Bart Schaefer" wrote:
> So I still can't reproduce what PWS reported (the "command not found" at
> line 153 of _main_complete).
I think that bit *was* style-dependent. I don't get it with zsh -f or on
my PC at home. For the rest it seems to be what you find.
--
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Work: pws@CambridgeSiliconRadio.com
Web: http://www.pwstephenson.fsnet.co.uk
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2000-07-08 22:22 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-07-07 16:12 completing directory path 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
2000-07-08 22:21 ` Peter Stephenson
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).