all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: chris <chris@bumblehead.com>, 71952@debbugs.gnu.org
Cc: chris@bumblehead.com, jgart <jgart@dismail.de>,
	Andrew Tropin <andrew@trop.in>
Subject: bug#71952: documentation inaccuracy?
Date: Tue, 09 Jul 2024 19:08:24 +0200	[thread overview]
Message-ID: <87ed825w8n.fsf@gmail.com> (raw)
In-Reply-To: <Zog51cqjFL_ChZMt@guix-xps>

[-- Attachment #1: Type: text/plain, Size: 378 bytes --]

Hi,

>> $ guix home switch-generation -- -1
>> guix home: error: -1: extraneous command

Indeed, the command-line parser seems incorrect and inconsistent with
the documentation.

The culprit seems the procedure ’parse-args’ from ’guix-home’ command
inside the module (guix scripts home).

Hum, I guess something as the attached patch should fix the issue.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch --]
[-- Type: text/x-diff, Size: 422 bytes --]

diff --git a/guix/scripts/home.scm b/guix/scripts/home.scm
index b4c82d275f..5c39e83983 100644
--- a/guix/scripts/home.scm
+++ b/guix/scripts/home.scm
@@ -682,6 +682,8 @@ (define-command (guix-home . args)
       (match rest
         (() opts)
         (("--") opts)
+        (("--" n)
+         (alist-cons 'argument n opts))
         (("--" command ...)
          (match (assoc-ref opts 'action)
            ('container

[-- Attachment #3: Type: text/plain, Size: 22 bytes --]


WDYT?

Cheers,
simon

  parent reply	other threads:[~2024-07-09 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05 18:22 bug#71952: documentation inaccuracy? chris
2024-07-06 13:33 ` jgart via Bug reports for GNU Guix
2024-07-09 17:08 ` Simon Tournier [this message]
2024-07-09 18:58   ` jgart via Bug reports for GNU Guix
2024-07-31 13:43     ` Andrew Tropin via Bug reports for GNU Guix

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=87ed825w8n.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=71952@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=chris@bumblehead.com \
    --cc=jgart@dismail.de \
    /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.