From: Maxime Devos <maximedevos@telenet.be>
To: "Tommi Höynälänmaa" <tommi.hoynalanmaa@gmail.com>,
"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: RE: Exporting a nonexistent variable
Date: Tue, 5 Nov 2024 10:23:58 +0100 [thread overview]
Message-ID: <20241105102400.YxQ02D00H4tRJL606xQ0KJ@albert.telenet-ops.be> (raw)
In-Reply-To: <0effbe63-caee-a08b-77e0-576c3fe4b25c@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 72 bytes --]
I’ve send it to bug-guile, should appear in the issue tracker soon
[-- Attachment #2: Type: text/html, Size: 1101 bytes --]
next prev parent reply other threads:[~2024-11-05 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 12:26 Exporting a nonexistent variable Tommi Höynälänmaa
2024-11-04 20:43 ` Maxime Devos
2024-11-05 7:25 ` Tommi Höynälänmaa
2024-11-05 9:23 ` Maxime Devos [this message]
2024-11-05 9:26 ` Maxime Devos
2024-11-05 10:00 ` Tommi Höynälänmaa
2024-11-13 22:22 ` Attila Lendvai
2024-11-14 9:42 ` Maxime Devos via Developers list for Guile, the GNU extensibility library
2024-11-14 10:27 ` Mikael Djurfeldt
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=20241105102400.YxQ02D00H4tRJL606xQ0KJ@albert.telenet-ops.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=tommi.hoynalanmaa@gmail.com \
/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).