Re: manifest load error report.

2017-11-17 Thread Ludovic Courtès
Hi,

Mathieu Othacehe  skribis:

> When loading a manifest with an obvious error like "definee
> packages-list" instead of "define package-list", no error is reported,
> the "guix package -m manifest.scm command just exit with error 1.

Really?  I have this:

--8<---cut here---start->8---
$ guix package -m ~/t.scm
guix package: error: failed to load '/home/ludo/t.scm':
/home/ludo/t.scm:1:0: /home/ludo/t.scm:1:0: In procedure module-lookup: Unbound 
variable: definieee
$ cat ~/t.scm
(definieee foo bar)
--8<---cut here---end--->8---

> When using load instead of load* in a guile repl, the error is correctly
> reported :
>
> /home/mathieu/manifest.scm:1:0: /home/mathieu/manifest.scm:1:0: definee: 
> unbound variable
>
> Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
>
> Pusing a bit the investigation, it seems that in the pre-unwind-handler
> of load* in (guix ui), the "make-stack" call returns #f.

When ‘make-stack’ returns #f, that’s OK: it just means we won’t be able
to display a backtrace.

HTH,
Ludo’.



manifest load error report.

2017-11-13 Thread Mathieu Othacehe

Hi Guix,

When loading a manifest with an obvious error like "definee
packages-list" instead of "define package-list", no error is reported,
the "guix package -m manifest.scm command just exit with error 1.

When using load instead of load* in a guile repl, the error is correctly
reported :

--8<---cut here---start->8---
/home/mathieu/manifest.scm:1:0: /home/mathieu/manifest.scm:1:0: definee: 
unbound variable

Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
--8<---cut here---end--->8---

Pusing a bit the investigation, it seems that in the pre-unwind-handler
of load* in (guix ui), the "make-stack" call returns #f.

Any idea why ?

Thanks,

Mathieu