-
Notifications
You must be signed in to change notification settings - Fork 772
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
Add docs to explain whether move
supports directories as destination
#830
Comments
Sure, PR welcome. |
Just a friendly reminder that "PRs welcome" isn't really the best phrase to use. To people who file issues, it's effectively a polite way to say "if you want this, go do it yourself", and is one of those phrases that seemed like a good idea when it first popped up, but actually hurts a project more than it helps. A "Good idea!" response and then setting some labels like "docs", "enhancement", and "help wanted" to signal this probably won't get done by the core team itself unless someone has a spare moment is by far the more welcoming approach. (I will unfortunately not be filing that PR: I'm weeks deep into a 100+ page open source project documentation rewrite already, and have enough on my plate that filing docs improvement requests is the best I can do right now) |
Given that
mv somefile.txt textfiles
will happily move a filesomefile.txt
into a dirtextfiles
, one might expectmove('somefile.txt', 'textfiles')
to work, but the docs currently do not explain what a validdest
is. Could the docs be amended to make it explicit whetherdest
must be a file path, or whether any path is valid?The text was updated successfully, but these errors were encountered: