From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: missing quote in define-package arg
Date: Sun, 25 May 2014 09:53:26 +0200 [thread overview]
Message-ID: <87fvjyguq1.fsf@zigzag.favinet> (raw)
In-Reply-To: <87k39bosor.fsf@yandex.ru> (Dmitry Gutov's message of "Sat, 24 May 2014 22:57:56 +0300")
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
() Dmitry Gutov <dgutov@yandex.ru>
() Sat, 24 May 2014 22:57:56 +0300
Since -pkg.el files are not evaluated anymore in the latest version
of package.el, there's no syntax error.
Thanks for clarifying. To me, the key word here is "anymore", which
hints that there is some (internal) design skew, a signal that other
bugs / incompatibilities might be latent.
The only reason we see the warning is that the byte-compiler treats
the form contained in the file as a function application, whereas
essentially it's just data now.
Yes. It is "just" data now, though tantalizingly dressed in executable
(function application) form. So really, if the goal is to rid ourselves
of this temptation (so as to be able to focus on others :-D), would it
be correct to say that another option is to avoid generating that file
in the first place? Hmm, i wonder how we got to this state -- time to
go read the ChangeLog files...
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2014-05-25 7:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 7:18 missing quote in define-package arg Thien-Thi Nguyen
2014-05-24 8:02 ` Thien-Thi Nguyen
2014-05-24 11:32 ` Dmitry Gutov
2014-05-24 14:42 ` Thien-Thi Nguyen
2014-05-24 19:57 ` Dmitry Gutov
2014-05-25 7:53 ` Thien-Thi Nguyen [this message]
2014-05-25 17:05 ` Thien-Thi Nguyen
2014-05-26 0:19 ` Stephen J. Turnbull
2014-05-26 9:15 ` Thien-Thi Nguyen
2014-05-27 19:23 ` chad
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=87fvjyguq1.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).