- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
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.Yes, but this is the default on many distros, so for once the end user is not to blame
Even worse, many components will ignore the
XDG_DOWNLOAD_DIR
var so even if you manually change it to$HOME/downloads
(lower-case) it will often break things.Why not just
cd $XDG_DOWNLOAD_DIR
in the first place?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.
Something something symlink Downloads to downloads
Yeah but the main issue is that I don’t want there to be a
Downloads
directory in my home.
Keep filling those bugs and stop complaining on random forums, kids
Porque no los dos?
Lower case directories?
Eww
ILikeMineInAWayICanReadThemProperly, instead of ilikemineinawayicanreadthemproperly
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
CamelCase directories and snake_case files.
Do. none of you use case insensitive autocomplete? “do ” “Downloads”
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
No, it will probably go to “Documents”, and if you hit tab again it should go to “Downloads”. (Assuming you have the normal default folders)
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.
The choice of the letter d was brilliant, that’s for sure. Now I’m imagining 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
What shell would you recommend? 🤔
I use fish which is quite nice OOTB, although if you want a posix compliant shell, zsh with some plugins is also great.
Is fucking irrelevant. Just use your package manager.
Get some anger management help.
Maybe stop trying to be a smartass.
cd snuts
did you mean smuts?
You’ve come from Windows and have brought dangerous expectations.
MacOS has a case insensitive file system. It causes me untold grief
Is a 40 year old it guy who love linux, wat
Macos is case insensitive?!
OSX offers both case sensitive and case insensitive filesystems
Defaults to insensitive and if you want to change it you have to reformat 🥲
I’ve been using case insensitive fs on macOS for years and the only software having issues with this is onedrive.
can’t say i’m surprised.
i renamed my home folders to
dl
,docs
,pics
, etc. and use auto-cd (whatever its called) to just typedl
instead ofcd dl
Use Zsh or Fish and tab completion.
Or better yet, use z or zoxide:
“z down” will fuzzy match the “~/Download” folder.This is the way!
So you type
cd D
tab and it brings you toDocuments
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.
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.
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!
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/wiki/Dotted_and_dotless_I_in_computing
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.
Why are the Latin “a” and the Cryilic “a” THE FUCKING SAME?
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.