> Apologies, but what do you expect to happen to the file in-between the cut and the paste?
I'd expect that nothing will happen, Cut will wait for paste operation. It's not delete, where content is gone immediately. If no paste will follow, then Cut is not executed. Cut marks file for move operation, if no move is executed, then nothing will be lost.
> If I cut a sentence from a document and then cut another sentence, the first sentence is effectively gone (without an additional clipboard manager).
We're talking about files here, not text. Text behaves differently. I'd argue that Cut operation as it is in text editors, is not logical but it is what it is and people are used to it. For deleting there's Delete operation, Cut should not be equal to Delete in some occasions.
You are arguing that "copy and paste" and "cut and paste" in the context of a file manager actually behave as "mark, then copy" and "mark, then move" operations.
Well, that's exactly how Finder works, isn't it? Cmd+C marks files, Cmd+V copies them, Cmd+Opt+V moves them.
I'd expect that nothing will happen, Cut will wait for paste operation. It's not delete, where content is gone immediately. If no paste will follow, then Cut is not executed. Cut marks file for move operation, if no move is executed, then nothing will be lost.
> If I cut a sentence from a document and then cut another sentence, the first sentence is effectively gone (without an additional clipboard manager).
We're talking about files here, not text. Text behaves differently. I'd argue that Cut operation as it is in text editors, is not logical but it is what it is and people are used to it. For deleting there's Delete operation, Cut should not be equal to Delete in some occasions.