From: Gottfried <gottfried@posteo.de>
To: zimoun <zimon.toutoune@gmail.com>, help-guix@gnu.org
Subject: Re: how can I find the terminal output
Date: Sat, 30 Apr 2022 18:07:27 +0000 [thread overview]
Message-ID: <d6f8f97a-0476-985c-c26f-9ba3096a6173@posteo.de> (raw)
In-Reply-To: <86a6c3os7j.fsf@gmail.com>
Hi,
thanks for your answer,
> I entered "guix shell" in the terminal,
>>> and it created an empty environment.
I meant without any option, (just "guix shell") therefore it created an
empty environment.
(I didn't know what the guix shell is for. I just read the manual and
understood the purpose of 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.
Because I don't know how it works, I guessed that the "empty
environment" is a new created file which has been added and I wanted to
get rid of this file.
>> 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.
I am using the Bash terminal, Mate terminal in my case.
Opening the ~/.bash_history
tells me only my inputs, my commands, but it does not show what was the
output of my commands. Where I can find those in my Bash shell?
hope that makes my questions as a newcommer clear
Gottfried
Am 30.04.22 um 11:06 schrieb zimoun:
> 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
next prev parent reply other threads:[~2022-04-30 18:12 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
2022-04-30 18:07 ` Gottfried [this message]
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=d6f8f97a-0476-985c-c26f-9ba3096a6173@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@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.
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).