On 2/2/18 6:18 AM, Odne Hellebø wrote:
> Damn :) my email is in a changelog :D Thanks :)
Credit where credit's due.
> One thing though, is it possible to stop the cursor at the point it
> gets ambiguous? As in I have function
> foobar and fooBar if I do
> foo I will get foobar and if my intent wa
Damn :) my email is in a changelog :D Thanks :)
One thing though, is it possible to stop the cursor at the point it
gets ambiguous? As in I have function
foobar and fooBar if I do
foo I will get foobar and if my intent was to execute fooBar I
will have to go back and uppercase it. I think it would
On 2/1/18 3:40 PM, Odne Hellebø wrote:
> Is it something that you will consider adding to bash? I also saw something
> about the complete inbuilt command, is it possible through that?
I already did, and the version in the devel branch can do it.
--
``The lyf so short, the craft so long to lerne.
Is it something that you will consider adding to bash? I also saw something
about the complete inbuilt command, is it possible through that?
Just to spur the competition, zsh is able to do it ;)
On 29 January 2018 at 15:05, Chet Ramey wrote:
> On 1/28/18 8:10 PM, L A Walsh wrote:
>
> >>
> >> It
On 1/28/18 8:10 PM, L A Walsh wrote:
>>
>> It's all fine. He wants case-insensitive matching, which bash can be made
>> to do, and non-case-preserving completion, which readline does.
>>
>
> Bash can be made to do? W/o new code?
No, it takes a patch to enable case-sensitive matchi
Chet Ramey wrote:
On 1/27/18 3:38 PM, L A Walsh wrote:
Bash has the nocaseglob option, which ignores case on searching for
files via a wildcard. I don't believe there is an option to search
for functions ignoring case. So your "ab" will ignore case of
a file that is looked up. Bu
On 1/27/18 3:38 PM, L A Walsh wrote:
> Ilkka Virta wrote:
>> Doesn't Bash/readline already tab-complete file names so that the
>> completion fixes the case? If I do 'touch ABBA' and 'rm ab', it will
>> complete the name to 'ABBA'. It also completes 'ab' to 'ABBA' as the
>> name of a command if it's
Ilkka Virta wrote:
Doesn't Bash/readline already tab-complete file names so that the
completion fixes the case? If I do 'touch ABBA' and 'rm ab', it
will complete the name to 'ABBA'. It also completes 'ab' to 'ABBA'
as the name of a command if it's a binary in PATH, but if it's a
function, it
@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
* makeFood
* makeFoodl <- this does nothing
* makeFoodL-> expands to makeFo
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
>> M
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 B
On 1/26/18 5:57 AM, Odne Hellebø wrote:
> I have some functions that are very similar and would like to be able to
> tabcomplete those. The command is like makeFoodSpaghetti and
> makeFoodLasagne. I get tabcompletion for make but if the nextletter isn't a
> capital letter it doesn't work and ob
I have some functions that are very similar and would like to be able to
tabcomplete those. The command is like makeFoodSpaghetti and
makeFoodLasagne. I get tabcompletion for make but if the nextletter isn't a
capital letter it doesn't work and obviously need to have capital
letter for S and L
13 matches
Mail list logo
