From: Lele Gaifax <lele@metapensiero.it>
To: help-gnu-emacs@gnu.org
Subject: Re: Support for new Python 3.5 async/await keywords
Date: Fri, 25 Sep 2015 17:12:01 +0200 [thread overview]
Message-ID: <8737y2zg72.fsf@nautilus.nautilus> (raw)
In-Reply-To: 20150925120513.GA21939@tuxteam.de
<tomas@tuxteam.de> writes:
> 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).
Thank you, "make maintainer-clean" did the trick (I did execute a "make
distclean", and wrongly assumed that targets *.elc too, but it does not
(strangely, it removes them *only* in the admin/unidata dir)... I
should have checked!).
ciao, lele.
--
nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
lele@metapensiero.it | -- Fortunato Depero, 1929.
prev parent reply other threads:[~2015-09-25 15:12 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
2015-09-25 15:12 ` Lele Gaifax [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
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=8737y2zg72.fsf@nautilus.nautilus \
--to=lele@metapensiero.it \
--cc=help-gnu-emacs@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.
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).