From: Ricardo Wurmus <rekado@elephly.net>
To: 45914@debbugs.gnu.org
Subject: bug#45914: read skips space after colon when prefix keywords are enabled
Date: Sat, 16 Jan 2021 08:37:13 +0100 [thread overview]
Message-ID: <87lfctbady.fsf@elephly.net> (raw)
When prefix keywords are enabled with (read-set! keywords 'prefix) the
characters “: hello” are read as “#:hello” instead of two separate
symbols. It seems to me that only “:hello” should be read as “#:hello”.
There is no such problem with postfix keywords.
--
Ricardo
reply other threads:[~2021-01-16 7:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87lfctbady.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=45914@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).