From: Noam Postavsky <npostavs@users.sourceforge.net>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 25117@debbugs.gnu.org
Subject: bug#25117: 25.1.90; Result of called-interactively-p differs WRT file contents
Date: Mon, 5 Dec 2016 14:34:46 -0500 [thread overview]
Message-ID: <CAM-tV-_q=vXHywUagZHc-TQXWhSXeS_vnSn9QH6HnppiuCTcYw@mail.gmail.com> (raw)
In-Reply-To: <8a4cf1ca-0c91-47a5-fe70-afac35fbe08d@easy-emacs.de>
On Mon, Dec 5, 2016 at 2:38 PM, Andreas Röhler
<andreas.roehler@easy-emacs.de> wrote:
>>
>> The difference is lexical-binding: t, also happens at least as far back as
>> 24.3.
>
>
> Not sure about that. Checked with and without lexical-binding. Seems not
> making the difference. See png attached - with emacs -Q checked earlier and
> same result.
The text doesn't make the difference, it's the buffer-local value of
the lexical-binding variable that matters.
Having the text in the file affects the value indirectly, see
https://www.gnu.org/software/emacs/manual/html_node/emacs/Specifying-File-Variables.html
next prev parent reply other threads:[~2016-12-05 19:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 13:01 bug#25117: 25.1.90; Result of called-interactively-p differs WRT file contents Andreas Röhler
2016-12-05 16:18 ` Michael Heerdegen
2016-12-05 16:58 ` Andreas Röhler
2016-12-05 16:58 ` Michael Heerdegen
2016-12-05 17:18 ` Andreas Röhler
2016-12-05 17:39 ` Michael Heerdegen
2016-12-05 18:23 ` Andreas Röhler
2016-12-05 19:08 ` Noam Postavsky
2016-12-05 19:38 ` Andreas Röhler
2016-12-05 19:34 ` Noam Postavsky [this message]
2016-12-05 19:52 ` Andreas Röhler
2016-12-05 19:51 ` Noam Postavsky
2016-12-05 20:09 ` Andreas Röhler
2019-10-20 21:34 ` Lars Ingebrigtsen
2019-10-21 9:15 ` Michael Heerdegen
2019-10-21 12:21 ` Stefan Monnier
2019-10-21 13:21 ` Michael Heerdegen
2022-04-18 11:24 ` bug#25117: 25.1.90; `called-interactively-p' from edebug with lexical-binding always gives nil Lars Ingebrigtsen
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='CAM-tV-_q=vXHywUagZHc-TQXWhSXeS_vnSn9QH6HnppiuCTcYw@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=25117@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.de \
--cc=michael_heerdegen@web.de \
/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).