[Portland] command line interface inconsistancies

[Bastian, Waldo]

I think the use case for xdg-copy is rather limited compared to cp. I
don't think it has been given too much thought so far but I think it
should be used for accessing a single URI as passed to the application
by the desktop environment via either cut&paste or drag&drop. After all
the goal of xdg-utils is desktop integration. If you want to copy files
you can use cp already, and likewise, if you want to access websites you
can use wget already. Xdg-copy shouldn't target the usage models that
these tools already fulfil.

Waldo Bastian
Linux Client Architect - Client Linux Foundation Technology
Channel Platform Solutions Group
Intel Corporation - http://www.intel.com/go/linux
OSDL DTL Tech Board Chairman

>-----Original Message-----
>From: Whipple, Tom
>Sent: Monday, June 05, 2006 5:28 PM
>To: Bastian, Waldo
>Cc: portland at lists.freedesktop.org
>Subject: RE: [Portland] command line interface inconsistancies
>
>In general I like the idea of staying consistent with some convention.
The
>choice of one is not as important.
>
>Since you brought up xdg-copy, I think it makes sense emulate the cp
>command, in that you can do 'cp A B C somedir' and have files A,B,C be
>copied to somedir. Currently in the same situation, xdg-copy will
overwrite
>B with A and ignore C and somedir. At the very least xdg-copy should
>complain if it is called with more than two arguments.
>
>-tom