From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: swedebugia@riseup.net, 33755@debbugs.gnu.org
Subject: bug#33755: error: execlp: No such file or directory from guix environment
Date: Sun, 16 Dec 2018 17:05:31 +0100 [thread overview]
Message-ID: <8736qxtq2c.fsf@gnu.org> (raw)
In-Reply-To: <87efaiyu5c.fsf@ngyro.com> (Timothy Sample's message of "Sat, 15 Dec 2018 23:26:07 -0500")
Hello comrades!
Timothy Sample <samplet@ngyro.com> skribis:
> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
>> Hi Tim,
>>
>> I like it in princple, but why special-case ENOENT? I think it would
>> be better to just always print the program name (and maybe program
>> args, too!) and the system error message.
>
> You are right.
[...]
> From aedc745a3f9765ae00dc61a59fa53d22a458551b Mon Sep 17 00:00:00 2001
> From: Timothy Sample <samplet@ngyro.com>
> Date: Sat, 15 Dec 2018 23:17:46 -0500
> Subject: [PATCH] environment: Print command name on execlp error.
>
> Fixes <https://bugs.gnu.org/33755>.
>
> * guix/scripts/environment.scm (launch-environment): When execlp fails,
> include the command name in the error message.
Another option would be to do:
(set! execl
(error-reporting-wrapper …))
in (guix ui), as done for a few other procedures that have the same
issue.
WDYT?
Ludo’.
next prev parent reply other threads:[~2018-12-16 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 7:09 bug#33755: error: execlp: No such file or directory from guix environment swedebugia
2018-12-15 9:40 ` Julien Lepiller
2018-12-15 18:18 ` Timothy Sample
2018-12-15 18:35 ` Timothy Sample
2018-12-15 19:38 ` Danny Milosavljevic
2018-12-16 4:26 ` Timothy Sample
2018-12-16 16:05 ` Ludovic Courtès [this message]
2018-12-17 4:41 ` Timothy Sample
2018-12-18 9:05 ` 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=8736qxtq2c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33755@debbugs.gnu.org \
--cc=samplet@ngyro.com \
--cc=swedebugia@riseup.net \
/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).