unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Alex Branham <alex.branham@gmail.com>
Cc: 36157@debbugs.gnu.org, kaushal.modi@gmail.com
Subject: bug#36157: 27.0.50; ediff-files does not work after lexical-binding was enabled for ediff
Date: Sat, 15 Jun 2019 22:35:21 -0400	[thread overview]
Message-ID: <E1hcL0r-0001dZ-G6@fencepost.gnu.org> (raw)
In-Reply-To: <87r27wqaie.fsf@gmail.com> (message from Alex Branham on Fri, 14 Jun 2019 13:36:57 -0500)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > 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)

It should add prefixes to those variable names, to avoid conflict.

Then it could defvar those variables to make them always-dynamic.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







      reply	other threads:[~2019-06-16  2:35 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
2019-06-16  2:35       ` Richard Stallman [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=E1hcL0r-0001dZ-G6@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=36157@debbugs.gnu.org \
    --cc=alex.branham@gmail.com \
    --cc=kaushal.modi@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 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).