You could also say that down should not complete to download since those are completely different strings and you shouldn't expect one to get you the other.

[–] Feyter 4 points 1 year ago (1 children)

Sorry, down is a substring of download I don't get your point either?

[–] [email protected] 5 points 1 year ago (1 children)

Substring is not string.

If they were interchangeable, then "D" & "d" should be too.

[–] Feyter 3 points 1 year ago (1 children)

down matches down* because * also includes empty string. Also download matches down*

D matches D* but d is not matching D* because D is a different character than d.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

but why do we have to match specifically against substr*? it's not a law of nature, we could also match against the regex (?i)substr(?-i).*

not saying that one option is necessarily better, but I don't see a good reason for which any one of these options would be terrible

[–] Feyter 1 points 1 year ago* (last edited 1 year ago) (1 children)

Because usability. If you have the files down down1 down2 downxyz and download and the user only knows that it was "something with down" it's best to show the user everything matching "down*" and let the user decide what's the correct one.

Also I'm not sure but wouldn't your expression show everything if only one character would be entered?

And again I don't see this solving anything if the entered string actually contains other characters then what's in the file (D != d)

Yes one could argue that some form of advanced algorithm or even AI could be used to identify such use case like download and Download but this is programming Humor, not linguisic Humor.

[–] [email protected] 1 points 1 year ago

would it not be usable to have completion be case insensitive? I seem to be able to use that... if I only remember "something with down", I could just as easily forget the capitalization of "down". maybe I have downloads and Down? why not show everything matching case insensitively and let the user decide what's the correct one?

I didn't really understand what you thought the regex did incorrectly, but I think the regex works fine, at least for most implementations, anyways what I meant is just a case insensitive version of the regular substring completion, which shouldn't be too difficult to make.

The only thing it solves is the frustration of having to look for a file/directory twice because you didn't remember it's capitalization. again, those are different characters just like a do and downloads are different strings, but it can be easier for users if they can just press tab and let the computer fill the part of the name the don't remember (or don't want to type).

you don't need an advanced algorithm or and AI, there are many easy ways to make completion case insensitive (like that regex for example). Issues involving names are inherently somewhat linguistic, but either way interactive shells are meant to be (at least somewhat) usable to humans, and as seen by the post, some people would prefer completion to be case insensitive.