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
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.
There is truth in this, but it isn't as true as some people seem to think. it's true that trial and error is a real part of working in ml, but it isn't just luck whether something works or not. We do know why some models work better than others for many tasks, there are some cases in which some mannual hyperparameter tuning is good, there was a lot of progress in the last 50 years, and so on.
The comic itself is fine as a joke, but I really don't like how parents often don't take responsibility for their actions. Does the mother in this comic really had no reason to create another person, without their consent, knowing they will have to go through the hardships of life? sure, many times kids are overreacting but still, at least have the decency to respond truthfully and not change the subject.
I'm not sure having kids can be said to be "a deeply personal choice", it has to involve at least two other people, one of whom can't even express their opinion on the matter while they will be the one to experience the vast majority of the consequences.
technically lands are colorless, plains just produce white mana
otherwise everything seems fine and legal here
but relative to what? assuming portals work similarly to windows, if I take a hoop/window and place it quickly over an object, that object won't launch in the opposite direction
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
downloadsandDown? 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
doanddownloadsare 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.