From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)]
Date: Sun, 4 Jun 2017 11:52:03 +0200 [thread overview]
Message-ID: <20170604095203.GJ7145@seven> (raw)
In-Reply-To: <87wp8sw0wp.fsf@nicolasgoaziou.fr>
Mail von Nicolas Goaziou, Sun, 04 Jun 2017 at 11:35:34 +0200:
Hello,
> "Stefan-W. Hahn" <stefan.hahn@s-hahn.de> writes:
>
> > What I don't understand is, if I expand the pcase with (macrostep-expand) I
> > get the following:
> >
> > ,----
> > | (let (res)
> > | (dolist (pair (buffer-local-variables))
> > | (if
> > | (consp pair)
> > | (let*
> > | ((x
> > | (car pair))
> > | (x
> > | (cdr pair)))
> > | (let
> > | ((val x)
> > | (var x))
> > | (push
> > | (list 'set var val)
> > | res)))
> > | nil))
> > | res)
> > `----
> >
> > And this is obviously wrong.
>
> This is not obviously wrong. You may be thinking that both `x' symbols
> are the same, but they are not. E.g.,
>
> (let ((s1 (make-symbol "x"))
> (s2 (make-symbol "x")))
> (list (list s1 s2) (eq s1 s2)))
>
> =>
>
> ((x x) nil)
This I understand, but cannot see it in the macrostep-expanded code.
I will try learn more to understand this.
So it is obvoius now that you are a lisp magician of 8th grade. :-)
Thanks and kind regards,
Stefan
--
Stefan-W. Hahn It is easy to make things.
It is hard to make things simple.
prev parent reply other threads:[~2017-06-04 9:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 11:48 Bug: buffer local variables handled wrong [9.0.5 (release_9.0.5-497-g5bc540 @ /home/hs/.emacs.d/lib/org-mode/lisp/)] Stefan-W. Hahn
2017-06-03 20:46 ` Nicolas Goaziou
2017-06-04 6:57 ` Stefan-W. Hahn
2017-06-04 7:19 ` Nicolas Goaziou
2017-06-04 8:08 ` Stefan-W. Hahn
2017-06-04 8:24 ` Nicolas Goaziou
2017-06-04 9:18 ` Stefan-W. Hahn
2017-06-04 9:35 ` Nicolas Goaziou
2017-06-04 9:52 ` Stefan-W. Hahn [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170604095203.GJ7145@seven \
--to=stefan.hahn@s-hahn.de \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.