unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: 47875@debbugs.gnu.org
Subject: bug#47875: Elisp reader doesn't handle keywords
Date: Sun, 18 Apr 2021 18:05:02 +0200	[thread overview]
Message-ID: <b621db6fc49c9f4f59d4bf42ee22fca5155305ff.camel@student.tugraz.at> (raw)

Hi Guilers,

Using Guile 3.0.5, the elisp reader does not seem to support keywords
written in Elisp's preferred prefix-style notation (:keyword).

scheme@(guile-user)> ,L elisp
Happy hacking with Emacs Lisp!  To switch back, type `,L scheme'.
elisp@(guile-user)> :keyword
ice-9/boot-9.scm:1669:16: In procedure raise-exception:
Unbound variable: :keyword

Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
elisp@(guile-user) [1]> ,q
elisp@(guile-user)> (funcall (@ (guile) symbol->keyword) 'keyword)
$1 = #:keyword

Meanwhile in Emacs M-: :keyword yields :keyword.  Using Scheme-style
keywords also does not work:

elisp@(guile-user)> #:keyword
While compiling expression:
uninterned symbol cannot be saved to object file #<uninterned-symbol
keyword 7fb39fa4b5e0>

I think Guile should produce keyword objects for the former, so that we
don't need to talk about the latter.

Regards,
Leo






             reply	other threads:[~2021-04-18 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18 16:05 Leo Prikler [this message]
2021-05-13 22:43 ` bug#47875: Elisp reader doesn't handle keywords Taylan Kammer
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=b621db6fc49c9f4f59d4bf42ee22fca5155305ff.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --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).