Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mv files into a directory the same way you can with cp #176

Open
bitfield opened this issue Aug 15, 2022 · 1 comment
Open

mv files into a directory the same way you can with cp #176

bitfield opened this issue Aug 15, 2022 · 1 comment

Comments

@bitfield
Copy link
Contributor

I realise this applies to upstream too: it's a little confusing that you can't mv files into a directory the same way you can with cp:

mkdir new

# works
cp a.txt b.txt new

# doesn't work
mv a.txt b.txt new

-- a.txt --
-- b.txt -- 

Originally posted by @bitfield in #153 (comment)

To be clear, I'm not saying I have a convincing use case for this. It's just that, over many years and hundreds of students, I've developed a nose for what will confuse people trying to learn things.

I can already hear someone asking "Oh, cp works like Unix cp, so mv works like Unix mv?" Oh, my sweet, summer child.

@mvdan
Copy link
Collaborator

mvdan commented Aug 22, 2022

I agree. Want to send a patch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants