unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 55317@debbugs.gnu.org, Ryan Prior <rprior@protonmail.com>
Subject: [bug#55317] [PATCH] doc: Clarify guix shell's DWIM behaviour.
Date: Sat, 14 May 2022 11:16:58 +0200	[thread overview]
Message-ID: <87ee0wh3sl.fsf@gnu.org> (raw)
In-Reply-To: <9184428ce5f7de56848b1c0018b2639dd0e8a5ca.camel@gmail.com> (Liliana Marie Prikler's message of "Sun, 8 May 2022 17:29:06 +0200")

Hi,

Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:

> +++ 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.

It’s clearer like this, so go for it!  Maybe you can keep the @example
bit as that makes an easily visible anchor in the text.

Thank you,
Ludo’.




      parent reply	other threads:[~2022-05-14  9:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 15:29 [bug#55317] [PATCH] doc: Clarify guix shell's DWIM behaviour Liliana Marie Prikler
2022-05-08 15:29 ` [bug#55317] [PATCH v2] " Liliana Marie Prikler
2022-05-17 12:46   ` Ludovic Courtès
2022-08-16 19:16     ` bug#55317: " Liliana Marie Prikler
2022-05-09  1:33 ` [bug#55317] [PATCH] " Ryan Prior via Guix-patches via
2022-05-14  9:16 ` 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=87ee0wh3sl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=55317@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=rprior@protonmail.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 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).