all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Branham <alex.branham@gmail.com>
To: rms@gnu.org
Cc: 36157@debbugs.gnu.org, Kaushal Modi <kaushal.modi@gmail.com>
Subject: bug#36157: 27.0.50; ediff-files does not work after lexical-binding was enabled for ediff
Date: Fri, 14 Jun 2019 13:36:57 -0500	[thread overview]
Message-ID: <87r27wqaie.fsf@gmail.com> (raw)
In-Reply-To: <E1haWUk-0006Ia-CF@fencepost.gnu.org>


On Mon 10 Jun 2019 at 21:26, Richard Stallman <rms@gnu.org> wrote:

>   > If you look at the code of ediff-find-file, you will see the use of
>   > `symbol-value' everywhere.
>
> Which variables would this operate on?

I'm not 100% sure what you're asking here, but ediff uses variables to
store information and then passes those to functions. So in one function
it'll do something like this:

(setq file-A "/path/to/foo.el")
(setq buff-A (get-buffer-create "foo.el"))
(ediff-find-file file-A buff-A)

And then ediff-find-file uses (symbol-value 'file-A) to get the string
back. This breaks under lexical binding since the file-A argument
shadows the file-A global value.

I think it would be relatively easy to fix by just passing the values
themselves, but that'll break backwards compatibility if people outside
Emacs are relying on calling ediff functions this way.

Hope that clears things up,
Alex





  reply	other threads:[~2019-06-14 18:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10  3:11 bug#36157: 27.0.50; ediff-files does not work after lexical-binding was enabled for ediff Kaushal Modi
2019-06-10  3:21 ` Kaushal Modi
2019-06-10 13:41   ` Alex Branham
2019-06-10 13:45     ` Kaushal Modi
2019-06-10 15:37     ` Eli Zaretskii
2019-06-18 23:05       ` Glenn Morris
2019-06-11  2:26   ` Richard Stallman
2019-06-14 18:36     ` Alex Branham [this message]
2019-06-16  2:35       ` Richard Stallman

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=87r27wqaie.fsf@gmail.com \
    --to=alex.branham@gmail.com \
    --cc=36157@debbugs.gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=rms@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 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.