From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-user@gnu.org
Subject: Re: Unbound variable warning/exception
Date: Sun, 20 Dec 2020 22:36:29 +0100 [thread overview]
Message-ID: <878s9s88iq.fsf@gnu.org> (raw)
In-Reply-To: CA+XASoUjgZG4CsHtnGdw_6NK001f4f=5Q5tHxoejiAKuDzx00A@mail.gmail.com
Hi,
Aleix Conchillo Flaqué <aconchillo@gmail.com> skribis:
> On Fri, Dec 18, 2020 at 5:26 PM Christopher Lam
> <christopher.lck@gmail.com> wrote:
>>
>> Hi guilers, I saw in guix the incredibly useful unbound-variable exception
>> printer written by Ludovic. I've adapted for use in gnucash as
>> https://github.com/Gnucash/gnucash/commit/6f951784 -- there are now in
>> guile 3.0.4 many more unbound-var warnings than in 3.0.2 -- wouldn't it be
>> a useful hint to add to the warning in core guile as well?
>
> Wow, this is great!
>
> This should definitely be added to guile by default.
In Guix, the hint is displayed by an 'unbound-variable exception
handler, not by the 'unbound-variable printer; I think doing it in the
printer could be confusing.
Perhaps what could be done is export an 'unbound-variable handler that
does all this, and have the REPL use it?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-12-20 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 1:25 Unbound variable warning/exception Christopher Lam
2020-12-19 1:46 ` Aleix Conchillo Flaqué
2020-12-19 10:08 ` Massimiliano Gubinelli
2020-12-19 13:07 ` Christopher Lam
2020-12-19 16:30 ` Massimiliano Gubinelli
2020-12-20 21:36 ` Ludovic Courtès [this message]
2020-12-20 23:11 ` Christopher Lam
2020-12-21 10:48 ` Jérémy Korwin-Zmijowski
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878s9s88iq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@gnu.org \
/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.
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).