Re: mv missing destination operand message

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Jim Meyering on 9/25/2008 1:24 AM:
>> mv: missing destination file operand after `/u/karl/tmp/paper.ltx'
>>
> However, "file" is often used not to distinguish between symlink,
> directory, fifo, block device, etc, but rather to denote a generic file
> system "object", and that's the intent here.  That same diagnostic is
> also used in cp, ln, and install, so I'd like to keep it as is.

On the other hand, is there any reason why 'ln path/to/file' creates
'./file', while 'mv path/to/file' and 'cp path/to/file' complain?  For all
three apps, POSIX does not specify the one-argument case, so we are free
to choose the behavior that makes the most sense.  I'm wondering if adding
some consistency here would help matters (either make ln reject the
one-argument case, or make cp and mv treat the one-argument case as an
implicit '-t .').

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjbg2gACgkQ84KuGfSFAYCjowCfQJAuBuFPE27tEkwQqyATSFiK
qSkAnjgeevYBD6KGFuwEtsajVjt9zVJa
=UQ9W
-----END PGP SIGNATURE-----