[Portland] command line interface inconsistancies

Whipple, Tom tom.whipple at intel.com
Mon Jun 5 17:27:36 PDT 2006


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


-----Original Message-----
From: portland-bounces at lists.freedesktop.org
[mailto:portland-bounces at lists.freedesktop.org] On Behalf Of Bastian,
Waldo
Sent: Monday, June 05, 2006 4:39 PM
To: Martin Konold; portland at lists.freedesktop.org
Subject: RE: [Portland] command line interface inconsistancies

>Am Montag, 5. Juni 2006 18:30 schrieb Whipple, Tom:
>
>> I suggest that as in #1, required arguments have no dashes. As in #3
>> options with long names (eg --vendor) have two dashes. I would also
>> suggest that commonly used options have "shortcuts" (eg -h ==
--help),
>> where it makes sense.
>
>What about using the GNU/POSIX convention?

Well yes, but it doesn't really address the issue: why does
xdg-screensaver use "suspend" and not "--suspend" and why does xdg-menu
use "--user" and not "user" ?. Wrt GNU/POSIX: It's a bit awkward to
support -ofoo, -o=foo, and -abc from a script. Wouldn't hurt to support
"--" in xdg-copy though.

Cheers,
Waldo
_______________________________________________
Portland mailing list
Portland at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/portland


More information about the Portland mailing list