From: Ivan Sokolov <ivan-p-sokolov@ya.ru>
To: 47875@debbugs.gnu.org
Subject: bug#47875: Elisp reader doesn't handle keywords
Date: Fri, 04 Jun 2021 15:13:29 +0300 [thread overview]
Message-ID: <87sg1xomja.fsf@ya.ru> (raw)
In-Reply-To: <b621db6fc49c9f4f59d4bf42ee22fca5155305ff.camel@student.tugraz.at> (Leo Prikler's message of "Sun, 18 Apr 2021 18:05:02 +0200")
Leo Prikler <leo.prikler@student.tugraz.at> writes:
> Using Guile 3.0.5, the elisp reader does not seem to support keywords
> written in Elisp's preferred prefix-style notation (:keyword).
>
> Meanwhile in Emacs M-: :keyword yields :keyword. Using Scheme-style
> keywords also does not work:
>
> I think Guile should produce keyword objects for the former, so that we
> don't need to talk about the latter.
In Scheme keywords and symbols are separate entities, but in Elisp
keywords are just self-quoted symbols. I think your solution will cause
problems with Elisp algorithms that expect keywords to be symbolp.
next prev parent reply other threads:[~2021-06-04 12:13 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
2021-06-04 12:13 ` Ivan Sokolov [this message]
[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=87sg1xomja.fsf@ya.ru \
--to=ivan-p-sokolov@ya.ru \
--cc=47875@debbugs.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).