unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Omar Polo <op@omarpolo.com>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: let-alist can't deal with the keys which includes spaces.
Date: Tue, 20 Jul 2021 17:35:22 +0200	[thread overview]
Message-ID: <87h7gpyp51.fsf@omarpolo.com> (raw)
In-Reply-To: <CAGP6POJjbMkiqy4RgBwQHAGJjjKzJ0_25FtcLANMjA4cubYw7A@mail.gmail.com>


Hongyi Zhao <hongyi.zhao@gmail.com> writes:

> I adapted the examples given on
> <https://www.gnu.org/software/emacs/manual/html_node/elisp/Association-Lists.html>
> to the following:
>
> ;;;
> (setq colors '(("rose merry" . red) (lily (belladonna . yellow))))
>
> (let-alist colors
>   (if (eq ."rose merry" 'red)
>       .lily.belladonna))
> ;;;

It's not an error, it's totally expected.  When you type

	.lily.belladonna

emacs lisp (and I guess every lisp out there) sees the symbol
'.lily.belladonna.

Now, when you type

	."rose merry"

it just doesn't make sense (from the emacs lisp parser POV).  there's a
lonely dot and a string.  A lonely dot is not a valid symbol.  In
addition, remember that spaces aren't strictly necessary.  Consider for
example:

	(let ((.a 5))
	  .a"hello")
	;; => "hello"

	;; equivalent to
	(let ((.a 5))
	  .a
	  "hello")

Strings and symbols are different data types and such have different
properties and different syntax.

Moreover, I don't know how wise is to use strings as alist keys (symbols
are interned, strings doesn't necessary).  I suggest using something
like

	(setq colors '((rose-merry . red) (lily (belladonna . yellow))))

and following the kebab-case style.

HTH

> When I try to evaluate the above code snippet, the following error is triggered:
>
> Debugger entered--Lisp error: (invalid-read-syntax ". in wrong context" 8 28)
>   read(#<buffer *scratch*>)
>   elisp--preceding-sexp()
>   elisp--eval-last-sexp(t)
>   eval-last-sexp(t)
>   eval-print-last-sexp(nil)
>   funcall-interactively(eval-print-last-sexp nil)
>   call-interactively(eval-print-last-sexp nil nil)
>   command-execute(eval-print-last-sexp)
>
> It seems that let-alist can't deal with the keys which includes
> spaces. Any hints for this problem will be highly appreciated.
>
> Regards




  parent reply	other threads:[~2021-07-20 15:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 11:12 let-alist can't deal with the keys which includes spaces Hongyi Zhao
2021-07-20 12:49 ` tomas
2021-07-20 13:21   ` Hongyi Zhao
2021-07-20 14:56     ` tomas
2021-07-20 15:35 ` Omar Polo [this message]
2021-07-20 16:20   ` tomas
2021-07-20 16:52     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-20 17:08       ` tomas
2021-07-20 17:50         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-20 18:17           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-21  7:29             ` tomas
2021-07-21  8:46               ` Emanuel Berg via Users list for the GNU Emacs text editor

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7gpyp51.fsf@omarpolo.com \
    --to=op@omarpolo.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=hongyi.zhao@gmail.com \
    /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).