all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Felix Lechner <felix.lechner@lease-up.com>, 58908@debbugs.gnu.org
Subject: bug#58908: Position of '--check' makes or breaks 'guix shell'
Date: Wed, 02 Nov 2022 14:05:22 +0100	[thread overview]
Message-ID: <87zgd9ecbx.fsf@gmail.com> (raw)
In-Reply-To: <CAFHYt57cMhycKVDOMKmP_yT9-6cbRTsq8dUkMR=X54pLyO+dJQ@mail.gmail.com>

Hi,

On dim., 30 oct. 2022 at 14:57, Felix Lechner via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:

> For the Guix file below, which is also available here [1], the
> position of the --check makes or breaks the command.
>
> With
>
>     guix shell --development --check --file=guix.scm
>
> $ which autopoint
>
> which: no autopoint in
> (/home/lechner/.guix-home/profile/bin:/home/lechner/.guix-home/profile/sbin:/run/setuid-programs:/home/lechner/.config/guix/current/bin:/home/lechner/.guix-profile/bin:/home/lechner/.guix-profile/sbin:/run/current-system/profile/bin:/run/current-system/profile/sbin)
>
> while with
>
>     guix shell --development --file=guix.scm --check

It appears to me similar as #bug58859 [1].  The issue is that almost all
Guix subcommands process command line arguments from right to left.
When mixed «behaviour» argument as ’-D’ and «action» argument as
’--check’, it seems missing a plan to always process using the same
order.  Unrelated to “guix shell”, it had been discussed for “guix
package”, see [2].

1: <http://issues.guix.gnu.org/issue/58859>
2: <http://issues.guix.gnu.org/issue/50473>


Cheers,
simon




      reply	other threads:[~2022-11-02 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 21:57 bug#58908: Position of '--check' makes or breaks 'guix shell' Felix Lechner via Bug reports for GNU Guix
2022-11-02 13:05 ` zimoun [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=87zgd9ecbx.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=58908@debbugs.gnu.org \
    --cc=felix.lechner@lease-up.com \
    /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.