Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!uhccux!munnari.oz.au!bruce!monu1!vaxc!cie590l
From: hadgraft@civeng.monash.edu.au (Roger Hadgraft)
Newsgroups: comp.windows.ms
Subject: Re: Sad - Moving and Copying with File Manager
Message-ID: <29281.2678c7f0@vaxc.cc.monash.edu.au>
Date: 15 Jun 90 01:35:12 GMT
References: <9963@sbcs.sunysb.edu> <3130005@hplsla.HP.COM>
Organization: Civil Engineering, Monash University, Australia
Lines: 22

In article <3130005@hplsla.HP.COM>, davidr@hplsla.HP.COM (David M. Reed) writes:
>
> In line with the "little things" that irritate me.  A simple one is the
> copy/move under File Manager.  It is inconsistent.  If I select a file in
> one directory and tell it to copy to another directory, if the two directories
> are on the same drive it does a move.  (You have to use the CTRL key in
> combination with the mouse to mean "copy").  But if the two directories are
> on separate drives, then it does a copy.  (And I can't figure out how to make
> it do a "move", that is copy from first directory on first drive to second
> directory on second drive and then delete original.)  I would expect that
> move is move (irregardless if it is same drive or not) and copy and copy
> (irregardless if it is same drive or not).

You do a MOVE between different drives by holding down the ALT key. I agree that
it's inconsistent, but I rather prefer the default between drives to be COPY and
the default within a drive to be MOVE. Like so many things, we're biased by what
we've been used to in the past.
--
Roger Hadgraft                  |  hadgraft@civeng.monash.edu.au
Lecturer in Civil Engineering   |  phone:  +61 3 565 4983
Monash University               |  fax:    +61 3 565 3409
Clayton, Vic. 3168. Australia.  |