unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Gottfried <gottfried@posteo.de>, help-guix@gnu.org
Subject: Re: how can I find the terminal output
Date: Sat, 30 Apr 2022 11:06:56 +0200	[thread overview]
Message-ID: <86a6c3os7j.fsf@gmail.com> (raw)
In-Reply-To: <48436da2-0c29-79c1-66b2-e1ed4d0381fd@posteo.de>

Hi,

On Fri, 15 Apr 2022 at 20:15, Gottfried <gottfried@posteo.de> wrote:
> I entered "guix shell" in the terminal,
> and it created an empty environment.

Empty environment means that nothing had been added, i.e., you have what
is defined by the current PATH from where you call “guix shell”.


> How can I find now the terminal output in order to find the empty 
> environment and to delete it?

I do not understand what you mean here.  Once in the environment “guix
shell”, just type exit to return to the original environment.

All the extra files required to create the environment are still in the
store, so if you run again “guix shell”, then the creation of the
environment will be really quick.

Note that if you run “guix pull” between two “guix shell”, you have no
guarantee that the same shell will be created.

At the next garbage collection (for instance, guix gc -F 5G), all these
extra files will be removed from your store, possibly.


> What are the general terminal commands in order to read the history of 
> the outputs?

It depends on your shell.  I guess you are using the default shell –
which should be bash – from your Linux distro.  Therefore, all the
history is in ~/.bash_history.

Well, I do not know how Bash manages the history of concurrent
sessions.  Other said, if you have 2 terminals open, i.e., two Bash
sessions, which is the session recorded?  But that’s unrelated to “guix
shell”. ;-)


Hope that helps,
simon


  reply	other threads:[~2022-04-30  9:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 20:15 how can I find the terminal output Gottfried
2022-04-30  9:06 ` zimoun [this message]
2022-04-30 18:07   ` Gottfried
2022-05-02  8:54     ` zimoun
2022-05-02 12:53       ` Tobias Geerinckx-Rice
2022-05-06 20:18         ` Gottfried
2022-05-07 15:42           ` zimoun
2022-05-09 11:42             ` Kyle
2022-05-09 16:21               ` Gottfried

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=86a6c3os7j.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=gottfried@posteo.de \
    --cc=help-guix@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.
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).