From: "Ludovic Courtès" <ludo@gnu.org>
To: lgcoelho@disroot.org
Cc: 73294@debbugs.gnu.org
Subject: bug#73294: "guix shell -- anything" does not look for manifests
Date: Mon, 30 Sep 2024 23:04:23 +0200 [thread overview]
Message-ID: <875xqc4zvs.fsf@gnu.org> (raw)
In-Reply-To: <86b8b6bd0f2a04c6febb78b5c91f7676@disroot.org> (lgcoelho@disroot.org's message of "Mon, 16 Sep 2024 14:40:23 +0200")
Hi,
lgcoelho@disroot.org skribis:
> Currently, if you have an authorized manifest available and want to run
> some command (for example htop) provided by the manifest, you need to
>
>
> $ guix shell
> $ htop
>
> as supplying a command for guix shell makes it to not look for
> manifests, and instead simply create a empty environment.
>
>
> $ guix shell -- htop
> guix shell: warning: no packages specified; creating an empty
> environment
> guix shell: error: htop: command not found
>
> Which doesn't seems a desirable behavior to me. Could we fix it?
This is the documented behavior: ‘manifest.scm’ and ‘guix.scm’ are read
only for interactive use, meaning without ‘--’:
https://guix.gnu.org/manual/devel/en/html_node/Invoking-guix-shell.html
The rationale for it is that non-interactive uses of ‘guix shell’ would
always be self-contained.
This was arguably a very conservative choice but I’m not sure we can
change it at this stage. Thoughts?
Ludo’.
prev parent reply other threads:[~2024-09-30 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 12:40 bug#73294: "guix shell -- anything" does not look for manifests lgcoelho--- via Bug reports for GNU Guix
2024-09-30 21:04 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875xqc4zvs.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=73294@debbugs.gnu.org \
--cc=lgcoelho@disroot.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).