Re: [PATCH] environment: Add a prompt-name argument.

2016-10-27 Thread Ludovic Courtès
Roel Janssen skribis: > Ludovic Courtès writes: > >> Hi, >> >> Roel Janssen skribis: >> >>> This patch adds a -p and --prompt-name argument to @code{guix >>> environment}, and puts the argument's value between the square brackets >>> instead of "env". >> >> Sounds like a good idea! Maybe ‘--pro

Re: [PATCH] environment: Add a prompt-name argument.

2016-10-27 Thread Roel Janssen
;. I wanted to use --name first, but it doesn't explain why we would use -p for the short option instead of -n (which is already taken by --dry-run). WDYT? >>>From ea958e847019c94a2bde49285f1436dfec72e570 Mon Sep 17 00:00:00 2001 >> From: Roel Janssen >> Date: Thu

Re: [PATCH] environment: Add a prompt-name argument.

2016-10-24 Thread Ludovic Courtès
e a name? WDYT? >>From ea958e847019c94a2bde49285f1436dfec72e570 Mon Sep 17 00:00:00 2001 > From: Roel Janssen > Date: Thu, 20 Oct 2016 13:07:15 +0200 > Subject: [PATCH] environment: Add a prompt-name argument. > > * guix/scripts/environment.scm: Add --prompt-name (-p) argument. Some

[PATCH] environment: Add a prompt-name argument.

2016-10-20 Thread Roel Janssen
ing for the argument is (prompt-name). So, I have two questions: 0. Do you think we should apply this patch? 1. What name should the argument have? Kind regards, Roel Janssen >From ea958e847019c94a2bde49285f1436dfec72e570 Mon Sep 17 00:00:00 2001 From: Roel Janssen Date: Thu, 20 Oct 2016 13:0