On Jul 1, 2015 4:02 PM, "Thompson, David" wrote:
> On Wed, Jul 1, 2015 at 9:10 AM, Ludovic Courtès wrote:
> > I reckon it has the unfortunate property of not working out of the box
> > (except on GuixSD.) I’m sure many tools these days would choose to
> > hard-code a fancy colored PS1; while I
On Wed, Jul 1, 2015 at 9:10 AM, Ludovic Courtès wrote:
> "Thompson, David" skribis:
>
>> On Thu, Jun 25, 2015 at 7:45 AM, Ludovic Courtès wrote:
>>> Cyril Roelandt skribis:
>>>
+(define (run-shell shell env-name)
+ "Run the given SHELL, adding '(ENV-NAME) ' at the start of the prompt
"Thompson, David" skribis:
> On Thu, Jun 25, 2015 at 7:45 AM, Ludovic Courtès wrote:
>> Cyril Roelandt skribis:
>>
>>> +(define (run-shell shell env-name)
>>> + "Run the given SHELL, adding '(ENV-NAME) ' at the start of the prompt."
>>> + (cond ((string=? shell "/bin/bash")
>>> + (let
On Mon, Jun 29, 2015 at 10:41 AM, Ludovic Courtès wrote:
> "Claes Wallin (韋嘉誠)" skribis:
>> On Thu, Jun 25, 2015 at 3:28 PM, Ricardo Wurmus
>> wrote:
>>> 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 i
"Claes Wallin (韋嘉誠)" skribis:
> On Thu, Jun 25, 2015 at 3:28 PM, Ricardo Wurmus
> wrote:
>> Thompson, David writes:
>>> On Thu, Jun 25, 2015 at 8:02 AM, Ricardo Wurmus
>>> wrote:
Would it be feasible to give "GUIX_ENVIRONMENT" the package name as a
value instead of just "t"?
>>>
On Thu, Jun 25, 2015 at 10:00 PM, Claes Wallin (韋嘉誠)
wrote:
> On Thu, Jun 25, 2015 at 3:28 PM, Ricardo Wurmus
> wrote:
>> Thompson, David writes:
>>> On Thu, Jun 25, 2015 at 8:02 AM, Ricardo Wurmus
>>> wrote:
Would it be feasible to give "GUIX_ENVIRONMENT" the package name as a
v
On Thu, Jun 25, 2015 at 3:28 PM, Ricardo Wurmus
wrote:
> Thompson, David writes:
>> On Thu, Jun 25, 2015 at 8:02 AM, Ricardo Wurmus
>> wrote:
>>>
>>> Would it be feasible to give "GUIX_ENVIRONMENT" the package name as a
>>> value instead of just "t"?
>>
>> Not really, because 'guix environment'
Thompson, David writes:
> On Thu, Jun 25, 2015 at 8:02 AM, Ricardo Wurmus
> 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-
On Thu, Jun 25, 2015 at 8:02 AM, Ricardo Wurmus
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.
Up until now I have been using the $SHLVL environment variable to g
On Thu, Jun 25, 2015 at 7:45 AM, Ludovic Courtès wrote:
> Cyril Roelandt skribis:
>
>> +(define (run-shell shell env-name)
>> + "Run the given SHELL, adding '(ENV-NAME) ' at the start of the prompt."
>> + (cond ((string=? shell "/bin/bash")
>> + (let* ((directory (or (getenv "TMPDIR") "
Ludovic Courtès writes:
> Cyril Roelandt skribis:
>
>> +(define (run-shell shell env-name)
>> + "Run the given SHELL, adding '(ENV-NAME) ' at the start of the prompt."
>> + (cond ((string=? shell "/bin/bash")
>> + (let* ((directory (or (getenv "TMPDIR") "/tmp"))
>> +(t
Cyril Roelandt skribis:
> +(define (run-shell shell env-name)
> + "Run the given SHELL, adding '(ENV-NAME) ' at the start of the prompt."
> + (cond ((string=? shell "/bin/bash")
> + (let* ((directory (or (getenv "TMPDIR") "/tmp"))
> +(template (string-append directory "
12 matches
Mail list logo