unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lee Fallat <inbox@leefallat.ca>
To: guix-devel@gnu.org
Subject: [patch] Explain how to exit and clean up a guix environment
Date: Fri, 12 Feb 2021 17:45:50 -0500	[thread overview]
Message-ID: <99e3b475e2ae27c3326519cd961b1ce33cccb217.camel@leefallat.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

Hey,

It'd be useful to explicitly state how to do this. While my guess of
exiting the shell (or ctrl-d) was correct, not everyone will know!

Also there are people like myself who like to reduce storage usage if
possible on machines which don't have much, like on netbooks or ultra-
books. I've mentioned how to remove packages after exiting from the
environment.

I hope I'm submitting this patch correctly, if not let me know!

-- Lee

[-- Attachment #2: guix_environment_exit_and_clean.patch --]
[-- Type: text/x-patch, Size: 808 bytes --]

diff --git a/doc/guix.texi b/doc/guix.texi
index 68abb968b0..83a8205e2e 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -5558,6 +5558,11 @@ they should be defined in @file{.bash_profile}, which is sourced only by
 log-in shells.  @xref{Bash Startup Files,,, bash, The GNU Bash Reference
 Manual}, for details on Bash start-up files.}.
 
+Exiting from a guix environment is the same as exiting from the shell, and will
+place the user back in the old enviroment before @command{guix enviroment} was
+invoked. To remove the packages which were installed by @command{guix
+environment}, the garbage collector must be invoked using @command{guix gc}.
+
 @vindex GUIX_ENVIRONMENT
 @command{guix environment} defines the @env{GUIX_ENVIRONMENT}
 variable in the shell it spawns; its value is the file name of the

             reply	other threads:[~2021-02-12 23:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 22:45 Lee Fallat [this message]
2021-02-12 23:46 ` [patch] Explain how to exit and clean up a guix environment Tobias Geerinckx-Rice

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=99e3b475e2ae27c3326519cd961b1ce33cccb217.camel@leefallat.ca \
    --to=inbox@leefallat.ca \
    --cc=guix-devel@gnu.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).