From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Robert Cochran <robert+Emacs@cochranmail.com>
Cc: 29988@debbugs.gnu.org
Subject: bug#29988: 27.0.50; completing-read: Symbol’s function definition is void: internal-make-closure
Date: Fri, 05 Jan 2018 07:57:39 -0500 [thread overview]
Message-ID: <871sj4sbss.fsf@users.sourceforge.net> (raw)
In-Reply-To: <878tdcswj0.fsf@cochranmail.com> (Robert Cochran's message of "Thu, 04 Jan 2018 21:29:55 -0800")
Robert Cochran <robert+Emacs@cochranmail.com> writes:
> Starting from `emacs -Q` on the lastest Git master branch revision
> (1cc7bc0f6 "Improve backward compatibility in tramp-archive" at time of
> writing):
>
> 1) C-h v RET
> 2) Get error in minibuffer, instead of prompt to specify variable.
>
> A bisect appears to point to ce4865819 ("Fix command repetition with
> lexical-binding (Bug#29334)") to be the culprit. I'm afraid I'm not much
> help in coming up with a fix though.
I thought byte-compile-lambda received the source form, but it looks
like it actually gets some kind of semi-compiled thing (which happens to
be valid lisp for simple or non-lexical code). Getting the original
source form to that function looks to be pretty awkward; maybe the best
option is to revert the change and pursue the alternate methods
suggested by Stefan in Bug#29334.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29334#34
> At least for me, it took a very deep clean ('git clean -dXf' is what I
> used) for different checkouts to actually affect the result; doing a
> make distclean and *.elc removal on a known good build did not fix the
> error, only by doing the above Git command did I get any changes between
> checkouts.
Hmm, I would think removing elc, emacs, and emacs-bootstrap executables
should be enough.
next prev parent reply other threads:[~2018-01-05 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 5:29 bug#29988: 27.0.50; completing-read: Symbol’s function definition is void: internal-make-closure Robert Cochran
2018-01-05 12:57 ` Noam Postavsky [this message]
2018-01-07 2:50 ` Noam Postavsky
2018-01-07 9:42 ` Robert Cochran
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=871sj4sbss.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=29988@debbugs.gnu.org \
--cc=robert+Emacs@cochranmail.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.
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).