From: Florian Pelz <pelzflorian@pelzflorian.de>
To: 74418@debbugs.gnu.org
Cc: "Florian Pelz" <pelzflorian@pelzflorian.de>,
"Ludovic Courtès" <ludo@gnu.org>,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#74418] [PATCH] doc: Explain ‘--’ syntax of ‘guix shell’ before giving examples.
Date: Mon, 18 Nov 2024 15:38:57 +0100 [thread overview]
Message-ID: <24a645c2c44f8b98d6351c8d8c4839feb46b012e.1731940595.git.pelzflorian@pelzflorian.de> (raw)
This paragraph is present in the ‘guix environment’ docs. I presume
it clarifies ‘guix shell’ for newcomers as well.
* doc/guix.texi (Invoking guix shell): Take over an introductory
paragraph from ‘guix environment’ and use it for ‘guix shell’.
Change-Id: I06280516ad3436260114b074c5f325e6984e9c76
---
doc/guix.texi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guix.texi b/doc/guix.texi
index ba4bd2cc79..f71f0b6561 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -5933,6 +5933,10 @@ Invoking guix shell
guix shell [@var{options}] [@var{package}@dots{}]
@end example
+Sometimes an interactive shell session is not desired. An arbitrary
+command may be invoked by placing the @code{--} token to separate the
+command from the rest of the arguments.
+
The following example creates an environment containing Python and NumPy,
building or downloading any missing package, and runs the
@command{python3} command in that environment:
base-commit: 23cbbe6860782c5d4a0ba599ea1cda0642e91661
--
2.46.0
next reply other threads:[~2024-11-18 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 14:38 Florian Pelz [this message]
2024-11-18 15:00 ` [bug#74418] [PATCH] doc: Explain ‘--’ syntax of ‘guix shell’ before giving examples Ludovic Courtès
2024-11-18 22:32 ` Noé Lopez via Guix-patches via
2024-11-19 11:17 ` bug#74418: " pelzflorian (Florian Pelz)
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=24a645c2c44f8b98d6351c8d8c4839feb46b012e.1731940595.git.pelzflorian@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=74418@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.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.