Linux: Using Top
-
And actually, NTFS cares too. NTFS is case sensitive just like any other POSIX filesystem. NTFS is part of the POSIX family with EXT3, XFS, BtrFS, XFS, etc. It's actually the Windows Command Shell that strips this out. If you use BASH on Windows, everything is case sensitive again. It's a weird abstraction by the shell to make it all case sensitive under the hood, but presented to the end users differently.
-
I take it back then.
No one moving from Windows to Linux should have any issues with capitalization.
NOTE THIS IS SARCASM. IN ALL CAPS.
-
@BRRABill said in Linux: Using Top:
I take it back then.
No one moving from Windows to Linux should have any issues with capitalization.
NOTE THIS IS SARCASM. IN ALL CAPS.
They absolutely should not. It's not a Windows issue, its a cultural issue on Windows how ridiculous misuse of capitalization has been first accepted and then promoted. It's actually a bit crazy that even Windows users use it so oddly. It just doesn't make sense. It's been long enough since the no-lower case DOS days or the no shift key Apple ][ days that no one should be thinking of the world without capitalization today. Certainly no one on Windows since the Internet came about has actually been able to do that without things breaking. Abusing caps on Windows has made Windows users struggle unnecessarily all along.
-
@scottalanmiller said
its a cultural issue on Windows how ridiculous misuse of capitalization has been first accepted and then promoted. ... Abusing caps on Windows has made Windows users struggle unnecessarily all along.
You just supported my argument.
And I'm not necessarily even talking about filenames ... do you use a lot of Windows apps where CTRL-m and CTRL-M do different things? I sure don't.
-
@BRRABill said in Linux: Using Top:
@scottalanmiller said
its a cultural issue on Windows how ridiculous misuse of capitalization has been first accepted and then promoted. ... Abusing caps on Windows has made Windows users struggle unnecessarily all along.
You just supported my argument.
And I'm not necessarily even talking about filenames ... do you use a lot of Windows apps where CTRL-m and CTRL-M do different things? I sure don't.
Can't think of any that would NOT be case sensitive there. CTRL-x and CTRL-SHIFT-x are standardly case sensitive on Windows.
-
Any example of a little app on Windows you might use that is case sensitive... MS office.
-
And of course the OS itself is.
-
@scottalanmiller said in Linux: Using Top:
Can't think of any that would NOT be case sensitive there. CTRL-x and CTRL-SHIFT-x are standardly case sensitive on Windows.
How so?
They both do exactly the same thing.
-
@BRRABill said in Linux: Using Top:
@scottalanmiller said in Linux: Using Top:
Can't think of any that would NOT be case sensitive there. CTRL-x and CTRL-SHIFT-x are standardly case sensitive on Windows.
How so?
They both do exactly the same thing.
Not on Windows. Not on MS apps or any I know. What specialty app are you thinking of? And is it caused by having so few shortcuts that they double mapped them?
-
@scottalanmiller said in Linux: Using Top:
@BRRABill said in Linux: Using Top:
@scottalanmiller said in Linux: Using Top:
Can't think of any that would NOT be case sensitive there. CTRL-x and CTRL-SHIFT-x are standardly case sensitive on Windows.
How so?
They both do exactly the same thing.
Not on Windows. Not on MS apps or any I know. What specialty app are you thinking of? And is it caused by having so few shortcuts that they double mapped them?
I was just using Notepad. But I do see that in Word, CTRL+SHIFT+X does nothing. (Which is totally different than top where, for example, m and M both do different things.)
Do you have an example of where CTRL-[letter] and CTRL-SHIFT-[letter} actually do different things?
It's one things to just not have the SHIFT portion of it work, because why would anyone press SHIFT if they could more easily not. But it is another entirely to have each do something totally different.
-
@BRRABill said in Linux: Using Top:
@scottalanmiller said in Linux: Using Top:
@BRRABill said in Linux: Using Top:
@scottalanmiller said in Linux: Using Top:
Can't think of any that would NOT be case sensitive there. CTRL-x and CTRL-SHIFT-x are standardly case sensitive on Windows.
How so?
They both do exactly the same thing.
Not on Windows. Not on MS apps or any I know. What specialty app are you thinking of? And is it caused by having so few shortcuts that they double mapped them?
I was just using Notepad. But I do see that in Word, CTRL+SHIFT+X does nothing. (Which is totally different than top where, for example, m and M both do different things.)
Do you have an example of where CTRL-[letter] and CTRL-SHIFT-[letter} actually do different things?
It's one things to just not have the SHIFT portion of it work, because why would anyone press SHIFT if they could more easily not. But it is another entirely to have each do something totally different.
X was an variable for "a character" there. But Windows uses caps in handling of shortcuts. Each application makes their own choices, of course, but the Windows, Microsoft and the Windows ecosystem standard is to respect case. It is unique to file system names when accessed through the command shell or the NT shell that they are ignored. The OS, most applications, the filesystem - essentially everything is still case sensitive.
You can see why it is bad. Remove it in one little place and Windows users often think it applies in all kinds of places that it does not. It's very confusing. I know what it exists (compatibility with DOS) but it's super weird and backwards. It's literally a holdover from the 80s and feels like it.
-
But "respecting it" means nothing.
In WIndows, pressing a key for a function only does that function, or nothing.
I am taking about, for example, in top where
m
and
M
do two totally different things.
-
@BRRABill said in Linux: Using Top:
But "respecting it" means nothing.
In WIndows, pressing a key for a function only does that function, or nothing.
I am taking about, for example, in top where
m
and
M
do two totally different things.
Right, an in WIndows it always does two different things. If you keep using it in places where both do nothing, you can make ANYTHING into "not sensitive". But that logic, nearly every letter on the keyboard does the same thing - nothing. So you just told me that WIndows isn't "key sensitive". See why that makes no sense?
-
S scottalanmiller referenced this topic on
