I agree with Paul suggestion for an error message.
In any case, Coreutils 5.93 message was better than the current one
On Sat, Jul 22, 2023 at 8:37 PM Paul Eggert wrote:
> On 2023-07-22 03:19, Pádraig Brady wrote:
> > Given the subtleties in this area,
> > I'd be reluctant to adjust diagnostics
Thanks to both of you. I installed the attached into Savannah master
coreutils. It implements the suggestion, except that later I noticed
that EMLINK and ETXTBSY can join the throng.
At some point it might make sense to scan for other direct or indirect
calls to renameat, renameat2, and
On 22/07/2023 18:37, Paul Eggert wrote:
On 2023-07-22 03:19, Pádraig Brady wrote:
Given the subtleties in this area,
I'd be reluctant to adjust diagnostics here.
I looked into this a bit more. Given "mv dir e" where e/dir is an
existing nonempty directory, 7th Edition Unix fails this way:
On 2023-07-22 03:19, Pádraig Brady wrote:
Given the subtleties in this area,
I'd be reluctant to adjust diagnostics here.
I looked into this a bit more. Given "mv dir e" where e/dir is an
existing nonempty directory, 7th Edition Unix fails this way:
mv: e/dir exists
Solaris 10 mv fails
On 21/07/2023 18:17, Nir Oren wrote:
*mv: error message "Directory not empty" is confusing *
description: when you try to move a directory to a location already
containing a directory with the same name it would just write "mv: cannot
move 'A' to 'B': Directory not empty"
first, this is
*mv: error message "Directory not empty" is confusing *
description: when you try to move a directory to a location already
containing a directory with the same name it would just write "mv: cannot
move 'A' to 'B': Directory not empty"
first, this is technically a wrong error message because
