Insufficient error message on scheme errors

  • Open
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • nomike (they/them)
Owner
unassigned
Submitted by
nomike (they/them)
Severity
important

Debbugs page

nomike (they/them) wrote on 4 Feb 01:41 +0100
(address . bug-guix@gnu.org)
647df585-0bff-41ab-98f9-38bc43e774ca@nomike.com
The logging for guile errors is not sufficient when running `guix home
reconfigure`.

If you run the small self-contained example I've attached, the following
warning will be printed to the terminal:

> guix home: warning: unknown keyword or bad argument

There is an error in `prusa-slicer.scm`. If you rename it to
`prusa-slicer.scm~`, the warning is gone.

The bug here is, that the error message is very generic and doesn't tell
me what's going on. Via trial and error I can try renaming scheme files,
comment out sections of code, etc. and eventually track down the area of
the issue and then maybe spot the error there, but IMHO guix should
print more info to the terminal.

Something like this for example:

> guix home: warning: unknown keyword or bad argument 'foobar' in
./prusa-slicer.scm:12

would be much more helpful. Especially for noobs like me.

PS: This is not about the issue with `prusa-slicer.scm`, I know it's
wrong and bullshit ;-).
Ludovic Courtès wrote on 5 Feb 11:13 +0100
control message for bug #76040
(address . control@debbugs.gnu.org)
874j18bsy7.fsf@gnu.org
severity 76040 important
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 76040@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 76040
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch