- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or register to comment.
You’ve come from Windows and have brought dangerous expectations.
Why would case sensitive path names be considered dangerous?
This is a feature, not a bug
echo ‘set completion-ignore-case On’ >> ~/.inputrc
also idk does zsh do this automatically? don’t think i’ve ever had this problem except on legacy AF servers
i mean… unless you don’t tab complete, but then who doesn’t spam tab 30 times every keystroke?
Or up-arrow a bazillion time because you probably have it SOMEWHERE in the buffer, surely.
How does that handle languages that have different rules for capitalization? For example I and i are not the same letter in Turkish.
Don’t know actually, never used a language like that. But should be easy enough to undo should one test it and end up not liking how it handles it.
I believe that type of stuff is specified in your locale, so it’s possible that it would do the right thing if you’ve set your language to Turkish. Please try it and let us know though :)
Shit yo. How come I only learn this now? Thanks!
I don’t get it… “D” is a complete different character than “d” is.
It’s like wondering why “file1” is not opened when I typed in “file2”.
that’s not how language works though, in human language (i know this can be confusing) d and D are the same letter just in different forms.
It’s one thing to have case sensitivity in programs doing data manipulation, that makes sense because you don’t want the program to accidentally use the wrong files without supervision.
But when you have an interactive prompt you know what you’re doing, you can see if you entered the wrong directory, and you’re generally going to be working in directories that you have yourself organized.
Doesn’t tab completion solve this if there are no alternatives with matching case? sounds like a PBKAC
You could also say that
downshould not complete todownloadsince those are completely different strings and you shouldn’t expect one to get you the other.Sorry,
downis a substring ofdownloadI don’t get your point either?Substring is not string.
If they were interchangeable, then “D” & “d” should be too.
downmatchesdown*because*also includes empty string. Alsodownloadmatchesdown*DmatchesD*butdis not matchingD*becauseDis a different character thand.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
Because usability. If you have the files
downdown1down2downxyzanddownloadand 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.
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.
On Windows filenames are case insensitive at least usually, some people are used to that. But that is poor design for so many reasons, Turkish I being one of them.
Now take Android. Files are case-sensitive yet you can’t create 2 files with same name if they only vary in case.
One of the most pointlessly annoying things I’ve had to deal with was trying to move a process made for Linux onto a Windows MINGW/cygwin-type environment where one of the scripts would generate “.filename” AND “.FileName” files. :|
People want their computers to magically know what they want these days. :)
This specific problem doesn’t exist in oh-my-zsh config though. It will find the directory even if spelling it like this.
“magically know what they want” aka occasionally set you and your files on fire
i prefer not fire
using capital letters in file/directory names on Linux :|
It’s a default on some distros, unfortunately, and changing it without updating the necessary env vars will break a bunch of stuff.
It would be a default on almost every distro that follows XDG specifications to have stuff like Downloads, Pictures, Videos in the
$HOMEfolder. One of the first things I do as part of an installation is to modify~/.config/user-dirs.dirsand set a specific folder, say/data/downloadsor~/downloads, for every XDG base directory.
Use zsh and press tab
This. Except don’t use zsh because this is default in every single shell
Nope. Bash (at least by default on Ubuntu) doesn’t have case insensitive tab completion.
afaik there’s options you can turn on that enable it
search .inputrc and set completion-ignore-case On
Bash never does this by default
Bash has never not had tab completion out of the box for me
Tab completion is default, but completing an uppercase word by typing a lowercase letter is not
I can’t relate to this issue at all exactly because I use zsh. Also a little bit related but the fuck
So you type
cd Dtab and it brings you toDocumentsI seems that I have triggered something, but keep that going, it’s quality content generation. 😬
Everyone on any Linux thread ever: you are a moron, obviously and you’re doing it wrong. Why don’t you install another distro, or better yet: modify and recompile your distro to match your desired experience, the code is open source ffs! What do you need? 4 years of work maybe? Come on.
Anything that slightly improves UX is bloat.
True! I’ve got rid of my monitor a long time ago, who needs one? gshshhshshshhshbsbbs
I got rid of my whole computer a long time ago, now I just use rocks. Much less bloat.
bro that xkdc is gold
Op does not know about $CDPATH and tab completion keke
There are two Linux paradigms that I consider stupid. One is the use of centralized software repositories managed by the distro instead of individual developer maintained installers. The other one is file system case sensibility. They already admitted defeat on the first one with the rise of containerised applications. I wonder how much longer they’ll keep the charade on the second one.
Sorry, but you’re plain wrong on your first issue. Getting all your packages from one source is one of the biggest upsides of Linux.
Indeed, but I’m sure we can agree that it’s pretty stupid for every distro to maintain its own repo. That’s a lot of duplicate work, which could be spend on more useful things. Luckily flatpak is well on its way to change that
Hm… But different distros have different philosophies (not just) about updates. That’s part of why people choose a specific distro.
Theres still plenty speaking against flatpak (larger sizes, problems with GTK/qt themes, and it’s only meant for GUI applications - you still need a separate system for the kernel and lower-level/cli tools. And frankly, that makes flatpak unusable to me, because the purpose of a centralized package management system is not having duplicate systems).
So in short: y’all are gonna pry pacman from my cold, dead hand.
The same goes for me, but with Portage, brother.
I’m not against distros as a whole, some extra work will be inevitable because people have different preferences, but it feels like a waste having a Firefox package for arch, ubuntu, fedora and Debian while essentially all being identical. Indeed flatpak isn’t perfect yet, but it works great for me and it’s steadily improving
Pretty hilarious for mac users, of all people, to complain about centralisation. Like, don’t you live in a walled garden?
cd dow *tab
Here’s how to fix this[+]
Create
$HOME/.config/user-dirs.dirswithXDG_DOWNLOAD_DIR=“$HOME/downloads”
You may need to logout/in for things to reread this file.
The full list of keys is:
- XDG_DESKTOP_DIR
- XDG_DOWNLOAD_DIR
- XDG_TEMPLATES_DIR
- XDG_PUBLICSHARE_DIR
- XDG_DOCUMENTS_DIR
- XDG_MUSIC_DIR
- XDG_PICTURES_DIR
- XDG_VIDEOS_DIR
+: Since this is Linux, this is a fix for many but not all cases.
XDG User dirs are cool, i agree. But that’s not really the problem here
Just make a downloads folder if you absolutely want to go there
Symlink
mount bind
…why is it so hard to find a picture of a mountain with a harness on it
ln -s Downloads downloads FTW
But then you’re still accessing “Downloads” and not “downloads”
