From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: "Thompson, David" <dthompson2@worcester.edu>, 57467@debbugs.gnu.org
Subject: bug#57467: 'guix shell' does not honor default behavior when given a specific command to run
Date: Tue, 06 Sep 2022 09:18:45 +0200 [thread overview]
Message-ID: <87pmg90y3u.fsf@gnu.org> (raw)
In-Reply-To: <5a8e6b74-f936-2c15-390c-37e23a6365d8@telenet.be> (Maxime Devos's message of "Mon, 5 Sep 2022 21:53:20 +0200")
Maxime Devos <maximedevos@telenet.be> skribis:
> On 05-09-2022 15:06, Ludovic Courtès wrote:
>> The main difficulty here is that, should we eventually decide to change
>> behaviors, we’ll have to devise a migration timeline etc. (As an
>> example, we chose to keep ‘guix environment’ until at least May 2023;
>> all this must take time if we want to avoid breaking user workflows.)
>>
>> Thoughts?
>
> "guix shell" is for making packages available in the
> environment. Currently, "guix shell -- foobar" does not make any
> packages available -- it's effectively a no-op except for setting
> GUIX_ENVIRONMENT.
True, though you could always have scripts that read:
guix shell $packages -- whatever
and that will suddenly behave differently if $packages expands to an
empty string. Tricky!
Ludo’.
next prev parent reply other threads:[~2022-09-06 7:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 21:58 bug#57467: 'guix shell' does not honor default behavior when given a specific command to run Thompson, David
2022-08-29 1:28 ` Thompson, David
2022-08-29 10:29 ` Maxime Devos
2022-08-29 12:48 ` bug#57467: [EXT] " Thompson, David
2022-08-30 13:24 ` Maxime Devos
2022-08-30 13:39 ` bug#57467: [EXT] " Thompson, David
2022-08-30 14:33 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-08-30 16:22 ` bug#57467: [EXT] " Thompson, David
2022-08-30 19:26 ` bug#57467: [EXT] " Thompson, David
2022-09-05 13:06 ` Ludovic Courtès
2022-09-05 17:23 ` Thompson, David
2022-09-05 19:53 ` Maxime Devos
2022-09-06 7:18 ` Ludovic Courtès [this message]
2022-09-06 11:03 ` Maxime Devos
2022-09-06 11:33 ` Thompson, David
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=87pmg90y3u.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=57467@debbugs.gnu.org \
--cc=dthompson2@worcester.edu \
--cc=maximedevos@telenet.be \
/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).