Yeah the tech labor market has really proven that the idea of employment contracts being negotiated between equal parties isn’t true even in the best of circumstances.

Even when companies are desperate for talent, and willing to spend ridiculous amounts of money on salaries and perks, they are not willing to negotiate on anything outside of that. They still have terrifying contracts with non-compete and damages clauses they could use to wreck your life, no workplace democracy, unpaid overtime and whatever other shit is legal.

But hey! You get free snacks and enough money to buy the dinners you don’t time to cook and save up to survive your inevitable burn out!

Unless unions work differently where you live, they are a democracy that will pursue whatever issues its members vote on. If members don’t think pay is a problem, why would they try to change it?

You really can’t though. For several reasons. Which would have been apparent to you had you bothered to actually create your example link to http://аpple.com or to understand this problem.

This is likely because docker runs Linux in a VM on MacOS right?

We’ve had similar problems with stuff that works on the developers Mac but not the server which is case sensitive. It can be quite insidious if it does not cause an immediate “file not found”-error but say falls back to a default config because the provided one has the wrong casing.

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

I and l also look identical in many fonts. So you already have this problem in ascii. (To say nothing of all the non-printing characters!)

If your security relies on a person being able to tell the difference between two characters controlled by an attacker your security is bad.

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 :)

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!