From: Phil <phil@beadling.co.uk>
To: help-guix@gnu.org
Subject: Guix implementation for bullet-train
Date: Tue, 09 Mar 2021 20:31:40 +0000 [thread overview]
Message-ID: <85blbsm5lf.fsf@beadling.co.uk> (raw)
Hi all,
I've implemented a basic Guix plugin for Oh-My-Zsh's Bullet Train theme.
I plan to add more functionality going forwards as I think of more use cases.
Bullet Train is a fancy console prompt that supports Python, Ruby, Git, AWS, etc
- by augmenting the command prompt with contextual about the current
console environment and directory location.
I based the Guix plugin on the Python virtualenv one - but thinking
about how to represent Guix environmental data, it's more complex than
virtualenvs as it's not just a binary virtualenv is active or not.
I've made some simple assertions below - if anyone has an opinion on
this let me know.
- Guix profiles can be stacked on top of each other, and the order is
relevant. Unlike virtualenvs, we can source many profiles and we need
to be able to visually reference this. I do this by listing profiles
in the order they were sourced from left to right:
.guix_profile ← my_profile ← some_other_profile
- Guix environments (excluding --pure) can also be added to this stack
with environments running on top of profiles, or you can source a
profile from inside an environment. However when an environment is
exited it and any profiles stacked on top of it are lost, and must be
pruned from the visual representation:
.guix_profile ← my_environment ← some_other_profile
But on exit from the environment the visual representation will be
pruned to this:
.guix_profile
Thanks,
Phil.
My fork:
https://github.com/falloutphil/bullet-train.zsh
My changes:
https://github.com/caiogondim/bullet-train.zsh/compare/master...falloutphil:master
reply other threads:[~2021-03-09 20:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=85blbsm5lf.fsf@beadling.co.uk \
--to=phil@beadling.co.uk \
--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).