To view parent comment, click here.
To read all comments associated with this story, please click here.
"Just as Mac OS or Gnome. MS has no control over this short of including a test suite that declines to run non-standards-compliant software. It's inevitable. "
Indeed but those inconsistencies still exist and does affect the user experience.
"I have yet to meet one person who's computer-savy enough to use cmd.exe but not enough to switch to classic. "
Sure, but that's not the point. I use classic too the few times I'm forced to use XP.
"So gterm disables one way of c&p but not the other, very inconsistent. "
No, it uses Chift-Ctrl-C etc, it's just that I dont ever use it. In fact, I dont even use gnome-terminal.
Indeed but those inconsistencies still exist and does affect the user experience.
Yes, but they're inherent to all DEs so they don't affect any relative advantage Windows may have over Linux.
Sure, but that's not the point.
In the case of an expert program, like a terminal, it makes no difference.
"So gterm disables one way of c&p but not the other, very inconsistent."
No, it uses Chift-Ctrl-C
So, it's not inconsistent not only despite but because it uses a different shortcut?
BTW. I don't have a osnews account (you probably guessed as much) and I'm not really familiar with the ratings system but why are your postings immidiatly modded up one point? I could understand it for the first few postings (actually I didn't because you were wrong of course =) but these last few of both of us are just useless discussions about obscure parts of cmd.exe so either you've got a fan club or someone really has too much time and modpoints.
MS has no control over this short of including a test suite that declines to run non-standards-compliant software. It's inevitable.
No it's not. There are things called HIG.
Gnome apps, even when not following the HIG, integrate in Gnome. Windows apps do not.
Even Microsoft apps do not integrate well with Windows.
I have yet to meet one person who's computer-savy enough to use cmd.exe but not enough to switch to classic
So now you admit that it is not integrated with Windows. And yet it comes with it. So you were wrong.
So gterm disables one way of c&p but not the other, very inconsistent.
Wrong again. Ctrl+C is standard to sigterm (I think) a process in a shell, so it's very consistent with the shell. When you use the shell, it takes precedence other the GUI, and you can STILL cut & paste.
gterm does not disable anything, shortcuts for cut & paste are still there, but different, which is a necessity, as it clashes with the shell.







Member since:
I'm talking about Windows, the platform, and I am stating that it is not as consistent as is commonly said, regardless of the flaws in GNOME, KDE or whatever.
It becomes definitly less consistent when you start adding 3rd party programs. Just as Mac OS or Gnome. MS has no control over this short of including a test suite that declines to run non-standards-compliant software. It's inevitable.
Aha, yes, it's different. cmd.exe will ALWAYS use the classic decor.
I have yet to meet one person who's computer-savy enough to use cmd.exe but not enough to switch to classic.
I use CLI all the time and in GNOME (and KDE and xterm etc etc) cut-n-paste is done exactly the same way as in any other app: middle-click.
The selection buffer is only one way of c&p. There's also the clipboard. So gterm disables one way of c&p but not the other, very inconsistent.
Now, I can certainly understand why Ctrl+C isnt used for copy in a terminal but, and correct me if i am wrong, there is NO keyboard shortcut at all for copy in cmd.exe.
Ctrl+C, you have to switch to mark mode first. I don't know if there's a way to do that with a shortcut but I think so because I sometimes do it accidentially (I'm mostly a Linux user, my knowledge of the intricacies of Windows is rather spotty)
Anyway, cmd.exe was just one of the examples so lets not get all hung up on it.
erm, *I* thought it was a joke because a terminal will always be different from other GUI apps.