From: Jean Abou Samra <jean@abou-samra.fr>
To: Olivier Dion <olivier.dion@polymtl.ca>,
Maxime Devos <maximedevos@telenet.be>,
guile-devel@gnu.org
Subject: Re: Are source locations broken?
Date: Sun, 1 May 2022 20:03:29 +0200 [thread overview]
Message-ID: <894f1958-9bb3-732b-73bd-e8daf35e572a@abou-samra.fr> (raw)
In-Reply-To: <87czgx2nh0.fsf@laura>
Le 01/05/2022 à 19:04, Olivier Dion a écrit :
> Any news on that bug?
Last time I looked, it seemed that there had been an oversight with
source locations having changed representation (becoming 3-element
vectors instead of alists with symbol keys). But since the bugfix
patch I have submitted for curried definitions with docstrings has
received no reaction, I didn't want to invest time without much
hope that the effort would pay off :-(
Jean
next prev parent reply other threads:[~2022-05-01 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 20:11 Are source locations broken? Jean Abou Samra
2022-03-25 20:22 ` Maxime Devos
2022-03-25 20:27 ` Maxime Devos
2022-05-01 17:04 ` Olivier Dion via Developers list for Guile, the GNU extensibility library
2022-05-01 18:03 ` Jean Abou Samra [this message]
2022-05-01 18:27 ` Maxime Devos
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=894f1958-9bb3-732b-73bd-e8daf35e572a@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=olivier.dion@polymtl.ca \
/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).