421 reputation
419
bio website
location
age
visits member for 2 years, 2 months
seen 45 mins ago

Shyy erny anzr - Naqernf Rvonpu


7h
awarded  Nice Question
14h
comment How to prevent `mv` from moving a collection of files into a single regular one?
Then we'll have to leave it at that. Sorry 'bout that. This has been extended far enough now.
15h
comment How to prevent `mv` from moving a collection of files into a single regular one?
@G-Man No! I'd never respond to my own comments (how silly would that be??) Again: I wondered throughout about this bit here: then you'll need to create ~/bin/mv (or some other appropriate directory) and have it do /bin/mv... Huh?? ~/bin/mv is in my $HOME, and /bin/mv is in the bin directory following / (the root directory). To me that's two entirely different pairs of socks. Where is the relation?
15h
comment How to prevent `mv` from moving a collection of files into a single regular one?
@G-Man Thanks, Sir for instructing a rookie like me. :) (Ugh, feels like back in school when the teacher spoke.) But to the point again: I actually meant env mv to be run in order to run the system's /bin/mv command (just like printf is a bash builtin and env printf will run the system version). But why you felt the need to have this simple issue turned to a 15-minute-long speech escapes me. :)
1d
comment How to prevent `mv` from moving a collection of files into a single regular one?
In this case, I'd prefer env mv. Less typing. :) As my local keyboard layout requires the SHIFT key to be pressed for a forward slash, I would always favor "slash-less" versions (if applicable).
1d
awarded  Yearling
1d
comment How to prevent `mv` from moving a collection of files into a single regular one?
No, it's simply purpose. I'd frequently wait several weeks or sometimes 2 months until I accept an answer. The reason is that some very knowledgeable people have a VERY loaded schedule and might only find time to give their (usually best) answer after a couple weeks. So I always find it just respectful to wait for them to stop by. Well, and if they really don't, I won't hesitate to hit the checkmark, for sure. Besides, I don't see why some people are always in a hurry so much on SE + its flavors. Easy does it, fellas. Don't jump the gun. :) This ain't your boss pressing on you.
1d
comment How to prevent `mv` from moving a collection of files into a single regular one?
Thank you very much for this most SNEAKY one-liner! Just think it were a +5 I gave you. :) Will make lots of trial-and-error attempts unnecessary.--- And you know too well why I made that remark. Just need to be on a machine that is straightly POSIX (doesn't happen too rarely), and I'm going to have the next problem right there. :)
1d
comment How to prevent `mv` from moving a collection of files into a single regular one?
Or - as you probably did not know - type ´ \mv ` instead of mv. This less known "trick" will cause the command with the backslash prepended to it to ignore any alias definitions.
2d
comment How to remove file with mv command?
Must be the most stupid exercise ever given by a teacher. Please ask him what he's smoking. Must be doggone good stuff.
2d
comment How to prevent `mv` from moving a collection of files into a single regular one?
Indeed. But thanks for the tips in any case. :) Who knows who'd be needing them sometime.
2d
comment How to prevent `mv` from moving a collection of files into a single regular one?
But even that criticism would be justified after all! Because I confess it might not be evident from my original post that in reality I'm trying to solve a more complex problem which I just broke down into a simple one to have the part solved which I can't solve on my own. This is because SE is not a "plzz do my homeworkz" site -- though often mistaken for that. (Unfortunately.)
2d
comment How to prevent `mv` from moving a collection of files into a single regular one?
If, instead, you'd done mv *90.mp3 90, then mv would have failed with the error message that "the target file is not a directory". Hah, yeah, why so complicated eh? I use your line and I'll be happy. Only in this trivial case, though. :) Because this is the normal way I ask my questions: I'd have them narrowed down for simplicity's sake. No one has objected to find so far considering that the 90's files might as well be scattered around in various subdirectories which I want to "catch" as well. If and only if they're always in one source directory, your mv line is applicable.
2d
comment How to move a file without preserving permissions
Excuse me, do you happen to mean NTFS ? Because this is a typical NTFS thing that I always get flooded with these pointless messages. I know I cannot preserve ownership information, but it would be nice if mv didn't tell me that a gazillion times because once would be enough. :)
2d
revised How to prevent `mv` from moving a collection of files into a single regular one?
deleted 50 characters in body
2d
comment How to prevent `mv` from moving a collection of files into a single regular one?
Heh, you've got a cynical sense of humor, you nut you! :-P Well, that was the file called the "one single file" in bold print in my OP. :)
2d
comment How to prevent `mv` from moving a collection of files into a single regular one?
Thank you so much! That should be my future life-saver then. I owe you one. (Just as a note, a friend of mine had made the very same mistake some years ago, so I feel I'm not alone.)
2d
comment How to prevent `mv` from moving a collection of files into a single regular one?
Thanks. (Hoping it's not one of those GNU-isms again, though.)
2d
revised How to prevent `mv` from moving a collection of files into a single regular one?
edited title
2d
revised How to prevent `mv` from moving a collection of files into a single regular one?
edited title