all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mike Swierczek <mike@swierczek.io>
Cc: guix-devel@gnu.org
Subject: Re: Guix command line flag consistency
Date: Sun, 23 Apr 2017 00:46:25 +0200	[thread overview]
Message-ID: <8737d0hxha.fsf@gnu.org> (raw)
In-Reply-To: <4d3b4372-311a-45b8-67b0-0732245fba6f@swierczek.io> (Mike Swierczek's message of "Sat, 15 Apr 2017 15:34:40 -0400")

Hello,

Mike Swierczek <mike@swierczek.io> skribis:

> On 04/15/2017 01:43 PM, Hartmut Goebel wrote:
>
>> Am 14.04.2017 um 22:57 schrieb Mike Swierczek:
>>> I'd much prefer if both the short and long command line arguments
>>> accepted their argument in any arrangement.
>> I also stumbled over "--show=foo" failing. I suggest guix should follow
>> the GNU command lien parsing conventions. Maybe this could be extended
>> with the possibility to unambiguous shorten long options.
>>
> Good idea on unambiguous shortening of long options.  That sounds good too.
>
> I don't mind trying to implement all of this, I just want to make sure
> the team likes the idea first.

An interesting option (heh!) would be to implement what argp does, which
is to allow users to write a prefix of the long option if it’s
unambiguous:

  https://www.gnu.org/software/libc/manual/html_node/Argp.html

Apart from that, the conventions we follow are indeed those:

  https://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html

though the parser we use, (srfi srfi-37), has small differences.

Ludo’.

      reply	other threads:[~2017-04-22 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 20:57 Guix command line flag consistency Mike Swierczek
2017-04-15 17:43 ` Hartmut Goebel
2017-04-15 19:34   ` Mike Swierczek
2017-04-22 22:46     ` Ludovic Courtès [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737d0hxha.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mike@swierczek.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.