Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
That wasn't innovating. That kind of multi-tasking prevaled in ancient times but yes, Apple brought real multi-tasking using less resources and power.
It isn't real multitasking. It's time splicing. Been around for years.

As for Cut&Paste, it's about damn time.
 
Doesn't dragging files to another folder already move them? Isn't that what Cut/Paste does?:rolleyes:
 
Doesn't dragging files to another folder already move them? Isn't that what Cut/Paste does?:rolleyes:

I'm sure you know that enough people don't want to have to reach for the mouse to move files. I rarely use a mouse in Finder, mainly navigating via the keyboard, but to move files, I have to use the mouse and the keyboard. I find it annoying.
 
There is still no short cut for Cut N Past under Lion.

But there is a solution:

MoveAddict

This is a great app which brings Cut N Past to Mac.

Check it out!
 
Doesn't for me. It does paste the file in the new location, but it doesn't remove (cut) the file from the original location. It copies and pastes. Is there something in Keyboard Shortcuts that I need to check?

GREAT NEWS!

cmd+option+V works like a charm here.:D

YOU'RE RIGHT!

I'm so freaking confused. Some of you guys have your keystrokes messed up.

Just tell me… is it possible to move a file in the Finder without having to drag the damn thing around with a mouse arrow?

If so I'll figure out how to do it. :)
 
I'm so freaking confused. Some of you guys have your keystrokes messed up.

Just tell me… is it possible to move a file in the Finder without having to drag the damn thing around with a mouse arrow?

If so I'll figure out how to do it. :)

Yeah, you have to copy the file and then paste it in Lion. I'd say it is a "copy/cut-paste" ... :D

cmd+c then cmd+opt+v should do the trick.
 
This can be turned on also in Snow Leopard, but after you execute the CMD+X the file goes directly to Trash. The same happens also in Lion. Nothing new about that.

Why in the world would they have the file go directly to the trash?


I can't tell you how many times I've lost track of what I was cutting-and-pasting in Windows, and thankfully if you mess up (like cutting a line of text before you finish your operation), Windows just places the files back where they were so at least they aren't deleted.


This is going to cause more problems than it solves... they should have just left it disabled.
 
Doesn't dragging files to another folder already move them? Isn't that what Cut/Paste does?:rolleyes:

Right, but sometimes you don't want to open another finder window. It can be really convenient to cut, then navigate to the folder you want the file moved to, then paste.
 
This is going to cause more problems than it solves... they should have just left it disabled.

It is disabled, you have to manually enable it via the Terminal.

The cut/paste in Lion people are talking about isn't technically cut/paste. You copy the file (cmd-c) and then use the Move Here command (cmd-opt-v) which moves the file instead of copying it, removing it from its original location. It's essentially cut/paste, but not listed as cut/paste in the OS menus.

This seems a far better implementation to me. I never understood the cut/paste mentality to move files. In all other instances, cut removes the item being cut, deleting it if something else is copied/cut over it. Why does it act differently just because it's a file? Yes, I realize it's so you don't accidentally delete files, but the usage is inconsistent.
 
It is disabled, you have to manually enable it via the Terminal.

The cut/paste in Lion people are talking about isn't technically cut/paste. You copy the file (cmd-c) and then use the Move Here command (cmd-opt-v) which moves the file instead of copying it, removing it from its original location. It's essentially cut/paste, but not listed as cut/paste in the OS menus.

This seems a far better implementation to me. I never understood the cut/paste mentality to move files. In all other instances, cut removes the item being cut, deleting it if something else is copied/cut over it. Why does it act differently just because it's a file? Yes, I realize it's so you don't accidentally delete files, but the usage is inconsistent.

Ahhh i get it. Yeah, that's how windows works for all practical purposes, just with different terminology.
 
To me it is just copy the file to another location, and when completed the original file is deleted. The move command is not precisely like that, but somehow they never provided a shortcut. Ridiculous of course since it saves so much time.
 
There are shortcuts:

Copy and Past:
1. cmd+c
2. cmd + v

Cut and Past:
1. cmd+c
2. cmd+option+v
 
It is disabled, you have to manually enable it via the Terminal.

The cut/paste in Lion people are talking about isn't technically cut/paste. You copy the file (cmd-c) and then use the Move Here command (cmd-opt-v) which moves the file instead of copying it, removing it from its original location. It's essentially cut/paste, but not listed as cut/paste in the OS menus.

This seems a far better implementation to me. I never understood the cut/paste mentality to move files. In all other instances, cut removes the item being cut, deleting it if something else is copied/cut over it. Why does it act differently just because it's a file? Yes, I realize it's so you don't accidentally delete files, but the usage is inconsistent.

Isn't text cut more like the anomaly? Pretty much any other thing you might cut is a file or some other non-text thing. So it marks it for cut and paste does the moving. Sometimes it would be nice if it worked like that for text too because if you cut/copy something else you lose the cutted text altogether.

Anyway, I much prefer the file stack in Path Finder. Just drop the files you want to use, browse to where you want them to go and drag and drop. Doesn't matter if you copy something in between.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.