From: <tomas@tuxteam.de>
To: Lele Gaifax <lele@metapensiero.it>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Support for new Python 3.5 async/await keywords
Date: Fri, 25 Sep 2015 14:05:13 +0200 [thread overview]
Message-ID: <20150925120513.GA21939@tuxteam.de> (raw)
In-Reply-To: <87fv23q741.fsf@nautilus.nautilus>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Sep 25, 2015 at 09:40:46AM +0200, Lele Gaifax wrote:
[no idea about the Python thing]
> [*] FYI, just for fun, I also tried to build it, doing a bootstrap on a clean
> tree, but the compilation failed with an error when temacs tried to load
> "cl-preloaded.el":
Perhaps a previous "make clean" helps. It helped in my case a couple
of times already (my unconfirmed hunch is that the build is picking
up some compiled .elc it shouldn't).
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlYFOHkACgkQBcgs9XrR2kZ05wCffDAp2RmQLSL4Flg/oAGeyNod
OZAAn2MjX7sCLWxHRRptdRG8RqeVbAQd
=obAo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-09-25 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 7:40 Support for new Python 3.5 async/await keywords Lele Gaifax
2015-09-25 12:05 ` tomas [this message]
2015-09-25 15:12 ` Lele Gaifax
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=20150925120513.GA21939@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
--cc=lele@metapensiero.it \
/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).