From: "Thompson, David" <dthompson2@worcester.edu>
To: Eric Bavier <ericbavier@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] scripts: Add 'environment' command.
Date: Thu, 9 Oct 2014 12:54:17 -0400 [thread overview]
Message-ID: <CAJ=RwfaHbyrUy4eJXk3-AR16_RxS9JrvGJe-C_yj1dVm+HGR_Q@mail.gmail.com> (raw)
In-Reply-To: <8738axw5kp.fsf@gmail.com>
On Thu, Oct 9, 2014 at 12:50 PM, Eric Bavier <ericbavier@gmail.com> wrote:
> David Thompson writes:
>
>> By default, running 'guix environment' spawns a new $SHELL process,
>> because it is usually what one would want to do. However, the '--exec'
>> flag can be used to specify the command to run.
>
> For this option, together with the --search-paths option, would it be
> possible to customize the syntax of the output from the
> show-search-paths function? This might be a question for other guix
> commands as well. Either the current shell or the shell from --exec
> might set variables in a different way. E.g. the user is using the
> "fish" shell, and doesn't want to spawn a new process, they should be
> able to::
>
> eval (guix environment --search-paths guile)
>
> Btw, fish uses 'set -x PATH "..."' to export PATH set to "..."
>
> Just a thought.
>
I have thought about this, too. I think it would be a good future
improvement for all guix commands that output search paths.
>> Finally, the '--load' flag can be used to read a package from a file
>> instead of searching $GUIX_PACKAGE_PATH.
>
> Could we instead have a -L or --load-path option like for `guix build`?
> This would be useful if the user wants to give multiple packages to
> `guix environment` that are all outside $GUIX_PACKAGE_PATH.
>
The -L flag also works to add to the load path. Lower-case 'l' calls
'load' on the given file and expects a package or list of packages in
return. For this I envision having a 'package.scm' or similar file
in my git repos so that I can run 'guix environment -l package.scm' to
create a development environment without altering load paths or having
'package.scm' define a module.
> I'm very excited for this.
>
Thanks for the feedback!
- Dave
next prev parent reply other threads:[~2014-10-09 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 22:48 [PATCH] scripts: Add 'environment' command David Thompson
2014-10-09 6:44 ` Alex Kost
2014-10-09 16:50 ` Eric Bavier
2014-10-09 16:54 ` Thompson, David [this message]
2014-10-09 17:26 ` Eric Bavier
2014-10-09 19:30 ` Ludovic Courtès
2014-10-10 2:32 ` David Thompson
2014-10-10 12:09 ` David Thompson
2014-10-10 16:37 ` Ludovic Courtès
2014-10-10 18:09 ` David Thompson
2014-10-10 20:47 ` Ludovic Courtès
2014-10-10 22:16 ` David Thompson
2014-10-11 10:35 ` Ludovic Courtès
2014-10-11 12:27 ` David Thompson
2014-10-11 21:52 ` Ludovic Courtès
2014-10-12 4:43 ` Setting environment variables in .bashrc vs .bash_profile Mark H Weaver
2014-10-12 21:10 ` Ludovic Courtès
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='CAJ=RwfaHbyrUy4eJXk3-AR16_RxS9JrvGJe-C_yj1dVm+HGR_Q@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=ericbavier@gmail.com \
--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).