3 ms·

Then name the feature "mark for move" in the case of files. Problem solved. In my experience no Windows user able to use keyboard shortcuts for copying files h

Then name the feature "mark for move" in the case of files. Problem solved. In my experience no Windows user able to use keyboard shortcuts for copying files has an issue with this difference.

meindnoch 3y ago
>Problem solved. But there is no problem. This is how the macOS file manager have always been working. If you prefer how it worked on Windows, why did you switch to macOS? When you visit a foreign country, do you go around and tell people how they do things all wrong because it's different from your home country? Isn't that entitled a bit?
- alpaca128 3y ago
  What I mean is Apple could add the Cmd-X shortcut and its behaviour with zero compromise for the existing functionality, making it consistent with all other desktop operating systems and in turn making Mac OS more beginner friendly. They could just add it and users like you wouldn't even notice. > When you visit a foreign country, do you go around and tell people how they do things all wrong because it's different from your home country? This is software, not a cultural tradition, and I claim that asking a corporation with 160k employees for a simple feature that exists everywhere else is not entitled.
  - meindnoch 3y ago
    File management in Finder uses the system-wide pasteboard APIs. If you place something on the pasteboard with Cmd+C, you can paste it in any app that supports file pasting, and get a context-dependent result. If you paste the file in Terminal, the file path is entered. If you paste it in Mail, the file is placed as an attachment. If you paste an image file in Photoshop, the image is placed as a new layer. It's a consistent system. Now, what should happen if you "cut" a file with Cmd+X and you paste it into Mail? The file is deleted from the original location, but still somehow attached to the email? There's no point in monkey-patching such a feature into macOS for the sake of appeasing recent Windows converts. It's like complaining why Pascal doesn't support braces instead of begin/end. It's a different system. Feel free to not use it.

Then name the feature "mark for move" in the case of files. Problem solved. In my experience no Windows user able to use keyboard shortcuts for copying files has an issue with this difference.

meindnoch 3y ago

>Problem solved. But there is no problem. This is how the macOS file manager have always been working. If you prefer how it worked on Windows, why did you switch to macOS? When you visit a foreign country, do you go around and tell people how they do things all wrong because it's different from your home country? Isn't that entitled a bit?

alpaca128 3y ago
What I mean is Apple could add the Cmd-X shortcut and its behaviour with zero compromise for the existing functionality, making it consistent with all other desktop operating systems and in turn making Mac OS more beginner friendly. They could just add it and users like you wouldn't even notice. > When you visit a foreign country, do you go around and tell people how they do things all wrong because it's different from your home country? This is software, not a cultural tradition, and I claim that asking a corporation with 160k employees for a simple feature that exists everywhere else is not entitled.
- meindnoch 3y ago
  File management in Finder uses the system-wide pasteboard APIs. If you place something on the pasteboard with Cmd+C, you can paste it in any app that supports file pasting, and get a context-dependent result. If you paste the file in Terminal, the file path is entered. If you paste it in Mail, the file is placed as an attachment. If you paste an image file in Photoshop, the image is placed as a new layer. It's a consistent system. Now, what should happen if you "cut" a file with Cmd+X and you paste it into Mail? The file is deleted from the original location, but still somehow attached to the email? There's no point in monkey-patching such a feature into macOS for the sake of appeasing recent Windows converts. It's like complaining why Pascal doesn't support braces instead of begin/end. It's a different system. Feel free to not use it.