From: Daniel Fleischer <danflscr@gmail.com>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: The cons syntax format used by use-package.
Date: Sun, 19 Sep 2021 10:04:48 +0300 [thread overview]
Message-ID: <m2bl4p9hbj.fsf@gmail.com> (raw)
In-Reply-To: <CAGP6POJuwXjA-CQASXY2ft3bYjCvsGm3X1BxNTKCROHYwA5Zww@mail.gmail.com> (Hongyi Zhao's message of "Sun, 19 Sep 2021 12:14:28 +0800")
Hongyi Zhao <hongyi.zhao@gmail.com> writes:
> Any hints for this phenomenon?
I don't know, but you can run 'pp-macroexpand-last-sexp' and see how the
expanded code looks like and it might give you hints why some versions
run while the others don't.
--
Daniel Fleischer
next prev parent reply other threads:[~2021-09-19 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 13:15 The cons syntax format used by use-package Hongyi Zhao
2021-09-18 13:21 ` Daniel Fleischer
2021-09-18 13:33 ` Hongyi Zhao
2021-09-19 4:14 ` Hongyi Zhao
2021-09-19 7:04 ` Daniel Fleischer [this message]
2021-09-19 7:41 ` Hongyi Zhao
2021-09-21 11:58 ` 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=m2bl4p9hbj.fsf@gmail.com \
--to=danflscr@gmail.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).