Command-drag no longer moves messages, just copies them

[khanklatt]

Version: 2008
Operating System: Mac OS X 10.4 (Tiger)
Processor: Intel
Email Client: Exchange

Not sure why this is, but clicking some messages, beginning to drag them, and then holding down the Command key to "move, not copy" the messages no longer works.

What changed? Only that my database got corrupted and I had to rebuild it this morning (don't ask), but after a successful rebuild I seem to have lost the ability to Command-drag move.

Yes, "Message..Move To..." continues to work as expected.

Yes, "Right-Click..Move To..." also continues to work as expected.

This is purely around the function of the Command key "Move" functionality.

Neither command key works to "Move, not Copy".

It is consistent (in that it doesn't work with either type of folder) regardless of whether the folder being attempted to "Move" to is on the Exchange server or on the local hard drive, but the other (menu-bar and right-click menu) move features work fine.

Yes, both command keys work as you expect for Command-P, Command-S, Command-C, so it's not my keyboard.

I looked through the Command-, settings and couldn't find anything that would cause/fix this, nor in the Exchange server "Account Settings..." pref pane.

A real head-scratcher?

 

[Diane Ross]

Not sure why this is, but clicking some messages, beginning to drag them, and
then holding down the Command key to "move, not copy" the messages no longer
works.

Try Option drag.

 

[khanklatt]

No modifier key works. I tried shift, Command, Ctrl, and Option.

Of course, the one that is supposed to work (and verified to work on a coworker's computer), but doesn't, is Command.

 

[khanklatt]

Problem fixed.

Specifically, I suspected that something was amiss when I tried copying and pasting in Terminal.app, and it didn't work.

In Terminal.app, going into Edit..Copy and Edit..Paste wouldn't even work (but it would in Entourage), which then indicated that this was a wider problem than just Entourage.

Sure enough, a reboot (imagine that) fixed the problem.

For the record, if anyone else should discover this thread, I'm running OS X 10.4.11.

 

[Diane Ross]

Sure enough, a reboot (imagine that) fixed the problem.

Hmm, strange symptom that was fixed by the reboot. Glad you found it before
we chased you around trying things.