bug#29315: info cp: documentation feedback

[Pádraig Brady]

On 16/11/17 03:36, kalle wrote:
> hello,
> here some mistakes/improvement proposals to `info cp' from me:
>
> -sentence "If the `--target": take away "failing that"?

It's better as is, to document that these are separate modes

> -sentence "descending into source directories": shouldn't it be rather
> "descending into SOURCE's directories"?

That could be interpreted as only descending one level

> And since `-r' and `-R' is the
> same: write "-r/-R" instead.

That would be less standard/searchable

> -option `-f': why is it written about _opening_ a file, e.g. "opened for
> writing" and not simply "writeable"?

There can be differing restrictions on various operations,
so we're being explicit about the truncation permission.

> What is meant by "removes it and
> tries to open it again"?

It creates a new file rather than rewriting an existing one.
I suppose that could be clarified. Patch attached.

> It is said "`cp' then removes it". It should be
> added ", if the user has write-permission in the containing directory."

There are other permissions that may block the unlink also.
It's better not to partially list potential issues,
and just state what cp does.

> -part "-i": shouldn't be written "When copying to a file" instead?

Subtly no, because we prompt if overwriting a dir with a file.
So the prompt depends on the source, not the dest.

cheers,
Pádraig.

cp-f-recreate.patch
Description: Text Data