On Sat, Aug 4, 2018 at 2:07 PM Warren Young <war...@etr-usa.com> wrote:
> > > https://hackaday.com/2018/01/19/linux-fu-custom-bash-command-completion/ There's one big caveat to doing so: trying to use features not explicitly allowed for by the programmable completion will break completion in annoying ways. e.g. when using my system-provided completion, which includes support for the sqlite3 shell, i cannot tab-complete sqlite3 database filenames unless they have the exact set of extensions defined by the completion rules. e.g. tying: sqlite3 myF<TAB> will not complete myFossilRepo.fsl because the programmable completion has a hard-coded list of file extensions it will expand. Likewise, the completion for the zip/unzip commands cannot tab-complete CBZ files, which are simply ZIP files with a different extension. (i use a lot of CBZ files, including manipulating them from the shell, so this limitation is severely annoying.) Thus... i disable all programmable completion on my systems. It just gets in the way, which i cannot abide. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
