all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 30872@debbugs.gnu.org
Subject: bug#30872: 26.0.91; odd byte compile issue
Date: Tue, 20 Mar 2018 19:57:28 -0400	[thread overview]
Message-ID: <877eq6ti53.fsf@gmail.com> (raw)
In-Reply-To: <m2y3in1m0p.fsf@gmail.com> (Aaron Jensen's message of "Mon, 19 Mar 2018 20:08:54 -0700")

[-- Attachment #1: Type: text/plain, Size: 375 bytes --]

retitle 30872 incorrect byte-compile of closure called from local funcalled function
found 30872 24.3
tags 30872 + confirmed
quit

Aaron Jensen <aaronjensen@gmail.com> writes:

> There's all sorts of weird stuff in that repro, and maybe someone can
> pare it down further, but most of it appears to be required.

I macroexpanded and reduced the result, ending up with this:


[-- Attachment #2: reduced test case --]
[-- Type: application/emacs-lisp, Size: 342 bytes --]

[-- Attachment #3: Type: text/plain, Size: 191 bytes --]


I can reproduce back to 24.3 (which is the earliest Emacs I have
running).  I expect the bug has been present since the introduction of
lexical scope.  Looks somewhat similar to Bug#24171.


  parent reply	other threads:[~2018-03-20 23:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  3:08 bug#30872: 26.0.91; odd byte compile issue Aaron Jensen
2018-03-20  5:41 ` Aaron Jensen
2018-03-20 23:57 ` Noam Postavsky [this message]
2018-05-30 22:55   ` bug#30872: incorrect byte-compile of closure called from local funcalled function Noam Postavsky
2018-06-08  0:33     ` Noam Postavsky
2018-06-08  2:43       ` Stefan Monnier
2018-06-11 12:36         ` Noam Postavsky
2018-06-11 15:29           ` Stefan Monnier
2018-06-16 22:37             ` Noam Postavsky

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877eq6ti53.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=30872@debbugs.gnu.org \
    --cc=aaronjensen@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.