GNU bug report logs - #55317
[PATCH] doc: Clarify guix shell's DWIM behaviour.

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
Subject: bug#55317: closed (Re: [PATCH v2] doc: Clarify guix shell's DWIM
 behaviour.)
Date: Tue, 16 Aug 2022 19:17:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#55317: [PATCH] doc: Clarify guix shell's DWIM behaviour.

which was filed against the guix-patches package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 55317 <at> debbugs.gnu.org.

-- 
55317: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55317
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 55317-done <at> debbugs.gnu.org, Ryan Prior <rprior <at> protonmail.com>
Subject: Re: [PATCH v2] doc: Clarify guix shell's DWIM behaviour.
Date: Tue, 16 Aug 2022 21:16:48 +0200

Am Dienstag, dem 17.05.2022 um 14:46 +0200 schrieb Ludovic Courtès:
> 
> > +As an added convenience, @command{guix shell} will try to do what
> > you
> > +mean when it is invoked interactively as in
> >  @example
> 
> I’d add a colon after “in” followed by a newline.
I pushed this in 131acaa28ded1455de291a83a8cdecab77b74a87 some while
ago (with the added colon), so I'm closing this now.

Cheers

[Message part 3 (message/rfc822, inline)]

From: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
To: guix-patches <at> gnu.org
Cc: Ryan Prior <rprior <at> protonmail.com>
Subject: [PATCH] doc: Clarify guix shell's DWIM behaviour.
Date: Sun, 8 May 2022 17:29:06 +0200

---
Bonjour Guix,

as can be seen from <http://logs.guix.gnu.org/guix/2022-05-08.log#164019>,
the way in which guix shell interactively does what you mean is open to
interpretation and different folks may mean different things when
specifying nothing.  Therefore, document guix' assumptions more clearly.

Cheers

 doc/guix.texi | 21 ++++++++++-----------
 1 file changed, 10 insertions(+), 11 deletions(-)

diff --git a/doc/guix.texi b/doc/guix.texi
index 5399584cb0..249c5956e2 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -5693,17 +5693,16 @@ before @command{guix shell} was invoked.  The next garbage collection
 (@pxref{Invoking guix gc}) may clean up packages that were installed in
 the environment and that are no longer used outside of it.
 
-As an added convenience, when running from a directory that contains a
-@file{manifest.scm} or a @file{guix.scm} file (in this order), possibly
-in a parent directory, @command{guix shell} automatically loads the
-file---provided the directory is listed in
-@file{~/.config/guix/shell-authorized-directories}, and only for
-interactive use:
-
-@example
-guix shell
-@end example
-
+As an added convenience, @command{guix shell} when invoked interactively
+without any other arguments will try to do what you mean based on the
+files it locates in the current directory or parent directories.
+If it finds a @file{manifest.scm}, it uses this manifest as though
+it was given via @code{--manifest}.
+If it finds a @file{guix.scm}, it uses this package file as though
+it was given via @code{--development --file}.
+In either case, the file will only be loaded if the directory it
+resides in is listed in
+@file{~/.config/guix/shell-authorized-directories}.
 This provides an easy way to define, share, and enter development
 environments.
 
-- 
2.36.0

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.