Yes, but this is the default on many distros, so for once the end user is not to blame
Porque no los dos?
Something something symlink Downloads to downloads
This is all fun and games until you try moving a backup to a file system that's case-insensitive
That's not an environment variable. It's defined in ${XDG_CONFIG_HOME:-$HOME/.config}/user-dirs.dirs.
Though you can use the xdg-user-dir DOWNLOAD command to get it automatically.
If a directory has multiple words in it I usually do kebab case: i-like-mine-in-a-way-i-can-read-them-properly. Both easier to read and type than pascal case.
For more complex filenames I use a combination of kebab-case and snake_case, where the underscore separates portions of the file name and kebab-case the parts of those portions. E.g. movie-title_release-date-or-year_technical-specifications.mp4
Use a shell with decent auto-completion. I have not been irritated by this in years.
Won’t autocomplete fail if you do “cd d” and then try the autocomplete?
Or is that what you mean by “decent” auto-completion?
bash's autocomplete fails (at least with default settings), but e.g. zsh can figure out what you mean
Not with a decent autocomplete. It will look for a folder starting with a small d and if it doesn't exist it looks at a folder with a large D.
I don't get what you mean. It doesn't matter if you write a uppercase or lowercase d
No. Zsh. It's pretty easy to have a nice auto compl. No need for omz. After knowing poweline10k I just use it and syntax highlight plugin, manually installed. There is no need to add entire omz.
I use fish which is quite nice OOTB, although if you want a posix compliant shell, zsh with some plugins is also great.
If you need to run a set of commands or a script with fish you can just toss them in a file and run bash file.sh. I have been daily driving fish for years and I don't even have think about it.
Get some anger management help.
I personally like xonsh despite the minor amount of wonkiness it has, it's so nice to have python available directly in your shell, it takes the "i don't care about the quality of my code i just want this shit to work with minimal effort"-ness of bash and turns it up to 13.
You've come from Windows and have brought dangerous expectations.
Is a 40 year old it guy who love linux, wat
Macos is case insensitive?!
Wow, I figured it'd be case sensitive, crazy, gotta make it more windows like I guess.
I don't know about dangerous, but case-insensitive Unicode comparison is annoying, expensive and probably prone to footguns compared to a simple byte-for-byte equality check.
Obviously, it can be done, but I guess Linux devs don't consider it worthwhile.
(And yes, all modern filesystems support Unicode. Linux stores them as arbitrary bytes, Apple's HFS uses... some special bullshit, and Windows uses UTF-16.)
If you did it would likely break something as it's one of only two characters not allowed in a file name (the other being null).
You can do a lot of funky stuff within the rules though, think about control characters, non-printing characters, newlines, homographs, emojis etc. and go forth and make your file system chaos!
Meanwhile fishshell:
cd snuts
This is completely unrelated to the meme at hand, but the title just reminded me that for a while, Merriam-Webster mistakenly included the word "Dord" to mean density - because an editor misread the entry for "D or d" as an abbreviation of density.
This is as stupid as it is funny. I love it <3
I am regularly disappointed that the word games I play on my phone don't accept 'dord.' They should, damn it! One of them accepts Jedi, ffs!
This is a feature, not a bug
Right? I rather not have a computer automatically autocorrect.
Yeah, and I think most shells will correct this case by pressing tab
Also, I constantly name files in the same directory the same thing except for case. In my ~/tmp directory I have unrelated foo.c (C source) and foo.C (C++ source).
.C came first. I don't usually use it though; I usually use .cc or .cxx, but if I'm making some tiny test source, I often use .C. I'm strongly opposed to the .cpp extension because calling C++ "CPP" leads to confusion with the preexisting (before C++) use of the initialism to refer to the C preprocessor. There's a reason why CPPFLAGS refers to preprocessor flags and CXXFLAGS refers to C++ flags.
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?
Shit yo. How come I only learn this now? Thanks!
I love how many people brought up the Turkish "I" as if everyone here is on the Unicode steering committee or just got jobs for Turkish facebook.
I, an English speaker, have personally solved the problem by not having a Turkish I in the name of my Downloads directory, or any other directory that I need to cd into on my computer. I'm going to imagine the Turks solve it by painstakingly typing the correct I, or limiting their use of uppercase I's in general.
In fact, researching the actual issue for more than 1 second seemingly shows that Unicode basically created this problem themselves because the two I's are just seperate letters in Turkic languages. https://en.m.wikipedia.org/...
If you nerds think this is bad try doing Powershell for any amount of time. It is entirely case-insensitive.
Why the FUCK did they make characters that look the same have different codepointers in UNICODE? They should've done what they did in CJK and make duplicates have the same codepointer.
Unicode needs a redo.
Well letters don't really have a single canonical shape. There are many acceptable ways of rendering each. While two letters might usually look the same, it is very possible that some shape could be acceptable for one but not the other. So, it makes sense to distinguish between them in binary representation. That allows the interpreting software to determine if it cares about the difference or not.
Also, the Unicode code tables do mention which characters look (nearly) identical, so it's definitely possible to make a program interpret something like a Greek question mark the same as a semicolon. I guess it's just that no one has bothered, since it's such a rare edge case.
In cases where something looks stupid but your knowledge on it is almost zero it's entirely possible that it's not.
The people that maintain Unicode have put a lot of thought and effort into this. Might be helpful to research why rather than assuming you have a better way despite little knowledge of the subject.
It would be a default on almost every distro that follows XDG specifications to have stuff like Downloads, Pictures, Videos in the $HOME folder. One of the first things I do as part of an installation is to modify ~/.config/user-dirs.dirs and set a specific folder, say /data/downloads or ~/downloads, for every XDG base directory.
Use Zsh or Fish and tab completion.
This is the way!
Never used or heard of it before but apparently zoxide is only for cd command, do you happen to know if there's some fuzzy match for in general?
At the moment what I do is history foo | grep -i "bar"
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.
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.
They cater to windows users that are used to the quirks of their broken system.
Doesn't fish basically fix this?
It's funny that you're getting down voted for telling the truth. Nothing to be subjective about either. 😅
Would hope so
Seems like poor configuration either default or not
yeah Fish tab completion works, but one thing I've noticed though is that tab completion for wrong case only works if there's no option with the correct case
e.g. if I have Downloads and Downloads2 then d with tab completion will become Downloads, but if I have Downloads and downloads2 it will tab complete to downloads2 and D will complete to Downloads
I've been meaning to look through the Fish documentation to see if I can change that and fuzzy search for history but never got around to it
The only thing that annoys me is having to wrap wildcard expressions in quotes when using e.g. the find command.
But then it looks more correct, so it's hard to argue with.
Nice, I didn't know that. I habitually forget the closing quote so this might save me some ire
Still not a default. Also it's not the same thing.
I remember having that when I used OhMyZsh, but after going back to a more bespoke config it doesn't work anymore. Also tried using zsh as a different user to ignore my own configs, that doesn't work either.
tldr, it's not default zsh behavior.
It's not default in zsh maybe, but it's default in the oh-my-zsh config most people use.
I ran zsh for a while without that config and manually configured everything and it also works, but takes quite a bit of web searching to find all the knobs to turn.
I don't think most people use oh-my-zsh. It's very popular, and a lot of people use it, but I think most is a stretch.
Either way, it's just a set of plugins and configs so of course you can get it to work on any setup. Just saying that it's not inherent to zsh, and you can probably get similar behavior in most shells with a similar config.
OMZ and TAB gang raise up!
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.
Is there also an option to only have 8.3 filenames? Those long names are so tiresome.
Honest question: is case sensitivity that important? Are there files named settings.ini and Settings.ini, for example, in the same folder that do different things?
I've seen a number of comments imply the possibility of case insensitive tab completion. Is this real and how do I do it?
I have multiple times fumbled with forgetting to capitalize something, only for the terminal to 'dunk' at me
For bash, this is enough:
# Bash TAB-completition enhancements
# Case-insensitive
bind "set completion-ignore-case on"
# Treat - and _ as equivalent in tab-compl
bind "set completion-map-case on"
# Expand options on the _first_ TAB press.
bind "set show-all-if-ambiguous on"
If you also add e.g.CDPATH=~/Documents, it will also always autocomplete from your Documents no matter which directory you're on.
Well completion-ignore-case is enough to solve this particular problem, the other options are just sugar on top :)
I'm going to add completion-prefix-display-length to these related bonus tips (I have it set to 9). This makes it a lot easier to compare files with long names in your tab completion.
For example if you have a folder with these files:
FoobarSystem-v20.69.11-CrashLog2022-12-22 FoobarSystem-v20.69.11.config FoobarSystem-v20.69.12 FoobarSystem-v20.69.12-CrashLog2023-10-02 FoobarSystem-v20.69.12.config FoobarSystem-v20.69.12.userprofiles
Just type vim TAB to see
...1-CrashLog2022-12-22 ...1.config ...2 ...2-CrashLog2023-10-02 ...2.config ...2.userprofiles
$vim FoobarSystem-v20.69.1
GNU Readline (which is what Bash uses for input) has a lot of options (e.g. making it behave like vim), and your settings are also used in any other programs that use it for their CLI which is a nice bonus. The config file is ~/.inputrc and you'd enable the above mentioned options like this
$include /etc/inputrc
set completion-ignore-case on
set show-all-if-ambiguous on
set completion-map-case on
set completion-prefix-display-length 9
There's probably some way to add it in bash, but if you install zsh and use the default options for everything, it just works! I especially love zsh for things "just work": not just tab completion for directories but also having completion for tools like git, docker, kubectl, etc is super easy, and you don't need any weird magic like in Bash if you want to use an alias with the same completion
Hmm, it didn't "just work" for me. I had to set it up recently:
zstyle ':completion:*' matcher-list '' 'm:{a-zA-Z}={A-Za-z}' 'r:|=*' 'l:|=* r:|=*'
That line needs to go in .zshrc. Maybe it's enabled by default with oh-my-zsh?
You have to try it but I think it still works. Aliases just replaced the text you typed with text in the alias, so if you append a subfolder to the alias it should also be appended to the command.
It's like using !! when navigating folders. You can do cd ~/Downloads and then !!/source and it resolves to cd ~/Downloads/source
I'm sure that still works with aliases. Then you'll have dl/source and Doenloads/source that are the same location. Using aliases will mean any script or program you may use that might point to them won't just create a new default folder that is then no longer the same location as the renamed one that you'll expect everything in
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.
Pretty hilarious for mac users, of all people, to complain about centralisation. Like, don't you live in a walled garden?
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.
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
Symlink
...why is it so hard to find a picture of a mountain with a harness on it
Here's how to fix this[+]
Create $HOME/.config/user-dirs.dirs with
XDG_DOWNLOAD_DIR="$HOME/downloads"
You may need to logout/in for things to reread this file.
The full list of keys is:
+: 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
Zoxide and cd down. ;)
Because you need to cd "path to directory" not cd "name" lol
Here is an alternative Piped link(s):
https://youtu.be/oavMtUWDBTM?si=0L2KD8y5Pl_nBt_U
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
Or use a nicer alternative like zoxide! :)
Or Windows ;)
@programming.dev
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
go to feed...
@programming.dev
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
go to feed...
Reasonable and sane behavior of
cd. Just get into the habit of always using lower case names for files and directories, that's how our forefathers did it.save