Thanks, I'll check it out. On Sat, 26 Apr 2025, 1:14 am Chet Ramey, <chet.ra...@case.edu> wrote:
> On 4/25/25 11:18 AM, Tanmay Jagtap wrote: > > *Dear Bash Maintainers,* > > > > I have encountered an issue with Bash autocompletion on my system. > > Specifically, a file beginning with three dots (e.g., ...Hiding-From-You) > > is autocompleted even when no dot (.) has been typed, which seems > > inconsistent with typical Bash behavior where hidden files are excluded > > from completion unless the input starts with a dot. > > I can't reproduce this using bash-5.2.37. I suspect this is the result your > programmable completion specification for `cat' produces. > > You can find out the completion specification for cat by running > `complete -p cat'. > > > > ldd $(which bash) > > # linux-vdso.so.1 (0x00007ffff7fc3000) > > # libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 > (0x00007ffff7e15000) > > # libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ffff7c00000) > > # /lib64/ld-linux-x86-64.so.2 (0x00007ffff7fc5000) > > Note: libreadline is *not linked*, suggesting this Bash binary may not be > > using readline, which may be relevant for the autocompletion issue. > > It's more likely that it means your version of bash is linked against the > static version of readline that is part of the bash distribution. > > Chet > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/ >
