From: Taylan Kammer <taylan.kammer@gmail.com>
To: 47875@debbugs.gnu.org, Leo Prikler <leo.prikler@student.tugraz.at>
Subject: bug#47875: Elisp reader doesn't handle keywords
Date: Fri, 14 May 2021 00:43:58 +0200 [thread overview]
Message-ID: <5ca7278b-83fd-2c90-83ab-647c7abeac12@gmail.com> (raw)
In-Reply-To: <b621db6fc49c9f4f59d4bf42ee22fca5155305ff.camel@student.tugraz.at>
This seems to have been fixed in the wip-elisp branch.
Note that the branch is a couple years old. There's a version
of the branch by Ricardo Wurmus (rekado) that's been rebased on
a newer version of Guile, though still not on 3.0:
https://git.elephly.net/?p=software/guile.git;a=shortlog;h=refs/heads/wip-elisp
- Taylan
next prev parent reply other threads:[~2021-05-13 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 16:05 bug#47875: Elisp reader doesn't handle keywords Leo Prikler
2021-05-13 22:43 ` Taylan Kammer [this message]
2021-06-04 12:13 ` Ivan Sokolov
[not found] ` <87lf7onwcp.fsf@ya.ru>
2021-06-05 21:14 ` Leo Prikler
2021-06-06 18:21 ` Ivan Sokolov
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=5ca7278b-83fd-2c90-83ab-647c7abeac12@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=47875@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).