Re: Feature request: tab completion on functions

[Odne Hellebø]

@Chet why wouldn't I be able to execute the result?

@Ilkka Virta you nailed it :)

I may have been slightly unclear on what I want. I have 2 functions
makeFoodSpaghetti and makeFoodLasagne.
* ma<Tab>
* makeFood<Cursor>
* makeFoodl<Tab>                 <- this does nothing
* makeFoodL<Tab>            -> expands to makeFoodLasagne

So I want to be able to write the lowercase l after makeFood and tab
complete to get the function that I want.

Did a quick test with scripts and that works.



On 26 January 2018 at 17:14, Chet Ramey <chet.ramey@case.edu> wrote:

> On 1/26/18 10:23 AM, Ilkka Virta wrote:
> > On 26.1. 16:36, Chet Ramey wrote:
> >> You want to be able to complete shell function names case-insensitively
> >> even though you won't be able to execute the result? I can see case-
> >> insensitivity for executables on a case-insensitive file system like
> >> Mac OS HFS+ or APFS, but shell functions?
> >
> > Doesn't Bash/readline already tab-complete file names so that the
> > completion fixes the case? If I do 'touch ABBA' and 'rm ab<tab>', it will
> > complete the name to 'ABBA'. It also completes 'ab<tab>' to 'ABBA' as the
> > name of a command if it's a binary in PATH, but if it's a function, it
> > seems to require the correct case. Sort of confusing, really.
>
> Well, let's look at it.
>
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                  ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/
>