"Claes Wallin (韋嘉誠)" <g...@clacke.user.lysator.liu.se> skribis:
> On Thu, Jun 25, 2015 at 3:28 PM, Ricardo Wurmus > <ricardo.wur...@mdc-berlin.de> wrote: >> Thompson, David <dthomps...@worcester.edu> writes: >>> On Thu, Jun 25, 2015 at 8:02 AM, Ricardo Wurmus >>> <ricardo.wur...@mdc-berlin.de> wrote: >>>> >>>> Would it be feasible to give "GUIX_ENVIRONMENT" the package name as a >>>> value instead of just "t"? >>> >>> Not really, because 'guix environment' accepts any number of packages. >> >> Oh, right. I forgot about ad-hoc environments and “guix environment >> -l”. >> >> I’m mostly using “guix environment” with a single package name, and for >> that purpose it would be nice if I could make the shell prompt indicate >> for what package this environment was created. I guess “t” as a value >> for “GUIX_ENVIRONMENT” will have to do then. > > As the variable is mostly meant for human-readable display, I think > setting it to "guix guile emacs" if those were the packages given, or > "mypackage.scm" if that was the file given, is strictly an improvement > over "t". What about --ad-hoc? People would start to have expectations about what this variable contains, and it seems difficult to guarantee that we can always give it a meaningful value. Ludo’.
