From: "jgart" <jgart@dismail.de>
To: help-guix@gnu.org
Subject: Guix Environment Best Practices: Shell Hooks, Creating directories, and More
Date: Wed, 20 Jan 2021 00:10:28 +0000 [thread overview]
Message-ID: <05d44060a25f7de72cba88553153a332@dismail.de> (raw)
Hello Guix!
Could someone share an example or advice on how to currently achieve the following nix shell hook with guix environment/manifests/gexps/...:
# define shell startup command
hooks = ''
# this allows mix to work on the local directory
mkdir -p .nix-mix
mkdir -p .nix-hex
export MIX_HOME=$PWD/.nix-mix
export HEX_HOME=$PWD/.nix-hex
export PATH=$MIX_HOME/bin:$PATH
export PATH=$HEX_HOME/bin:$PATH
export LANG=en_US.UTF-8
export ERL_AFLAGS="-kernel shell_history enabled"
'';
in mkShell {
buildInputs = inputs;
shellHook = hooks;
}
Taken from this blog post on using nix shell for developing elixir:
https://ghedam.at/15443/a-nix-shell-for-developing-elixir
Any help is greatly appreciated.
next reply other threads:[~2021-01-20 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 0:10 jgart [this message]
2021-01-21 12:42 ` Guix Environment Best Practices: Shell Hooks, Creating directories, and More Joshua Branson
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=05d44060a25f7de72cba88553153a332@dismail.de \
--to=jgart@dismail.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).