Linked by Thom Holwerda on Sat 7th Mar 2009 23:47 UTC
Mac OS X Thanks to Ars Technica, we've got some Snow Leopard goodness for you. As always, Apple is quite secretive about its upcoming operating system, so even though test builds are released every now and then, information is scarce. An Ars reader has given some more insights into the latest Snow Leopard build, released on Friday.
Permalink for comment 352239
To read all comments associated with this story, please click here.
Member since:

That doesn't make it the proper behaviour. I'm not saying it's wrong - I'm just saying that "because it has always been like that" is not a reason not to change something.
Personally, "enter" means process, activate to me. Renaming with enter is just weird, and I've been a Mac user for a very long time.

But because in Windows and Linux it is differnt IS a reason to change it? Just because you're used to it?
I don't believe you that you've "been a Mac user for a very long time". Maybe if "long time" means "more than 2 weeks" to you. I used Windows for 5 years, followed by 3 years Linux. Since then (1 1/2 years) I'm using OS X. Guess what, I'm used to rename with Enter since several months and it really is helping to "enter, rename, enter. bam. done." OR "cmd-down several directories followed by cmd-down start the document I was looking for".

Uhm, yes, it actually does. If you select some text in document Xyz, and paste it to document Abc, it gets appended after wherever the cursor is in document Abc - leaving the text in the target document intact - merging the two.

A file is a file. Text is text. Mixing those two to produce irrelevant and confusing arguments is stupid.

When copying/pasting directories, merging should be the default because it's non-destructive and fits in better with other cases of copy/paste (like text). You could always implement a modifier to enable replace.

You could also implement a modifier to enable merge. To follow your logic (and avoid the stupid text vs file comparison, instead showing you an example file vs folder example): If I copy a file I can replace it if it exists. If I copy a folder it should replace a folder if it exists. Guess what: that's what the Finder does.

This has nothing to do with the discussion at hand, but Mac OS X has the same problems. Try deleting a file that's in use. Good luck hunting down which application is currently using it!

Congratulations! You really did NOT use OS X for a significant time. Otherwise you would know that renaming and moving files to the trash is indeed possible when it's in use by an application.

The Finder is one of the most maligned parts of the Mac OS. Even in Leopard, it is still a very cumbersome and limited file manager, which is why it receives so much ire from most reviewers.

Yes, revieweres like you are right.

Reply Parent Score: 0