You're viewing a single thread.
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).
Chaotic evil
Why not .cpp for C++? I don’t use C++, but I thought that was the standard.
.Ccame first. I don't usually use it though; I usually use.ccor.cxx, but if I'm making some tiny test source, I often use.C. I'm strongly opposed to the.cppextension 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.Just use
.C++But then the filename wouldn't be
/^[[:alnum:]._-]*~*$/.
Permanently Deleted
Why did Linux systems go for capitals in the home folder? It's actually kind of annoying and takes extra key presses.
....A while later "XDG Base Directory Specification"
Permanently Deleted
Any help with that?
Permanently Deleted
Symlink your desired location on the target disk to the place the system thinks the software should go. (In my case, /usr/local/games is a symlink to a different drive.)
Thanks
XDG specifies the capital names, but to be nitpickingly technically precise, linux systems don't do this. It mostly is done by the distribution maintainers, and the XDG specs. A base system does not usually have a notion of anything beyond your $HOME.
Try adding a user:
sudo adduser basicuser. If youls -al ~basicuseryou will see it's almost empty, just the .bashrc (or in my fedora, there's some .mozilla crap in /etc/skel that also gets bootstrapped).
I like you style