On Wed, Jul 19, 2023, 18:57 Grisha Levit <grishale...@gmail.com> wrote:
> On Wed, Jul 19, 2023 at 9:07 AM Chet Ramey <chet.ra...@case.edu> wrote: > > > > On 7/18/23 10:01 PM, alex xmb ratchev wrote: > > > i in 5.2.15 bash aarch64 termux did > > > > > > $ cp -ap db2.*/<tabtab> > > > > > > and got > > > > > > db2.i5// db2.i7// > > > > I can't reproduce this. > > This is a combination of either visible-stats or mark-directories > being on, filename completion being active, and the word being > completed ending with a slash and referring to an existing directory. > i dont get the first part at all $ INPUTRC=/dev/null bash --norc > bash-5.3$ cd /tmp > bash-5.3$ mkdir bin bld > bash-5.3$ cd b*/ > bin// bld// > > bash-5.3$ complete -W 'bin/ bld/' -o filenames x > bash-5.3$ x b > bin// bld// > > Also I think this is not a bug -- readline is asked to append a slash > to directory names and it does so. Same thing happens with e.g. `ls', > when asked to append a slash to directory names and the supplied name > already has a slash: > well imo its 'a bit bug' depends on apps meta codings , whenever recognize is-already or not $ ls -dp /var/ > /var// >
