unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: "David Dynerman" <emperordali@block-party.net>,
	25132@debbugs.gnu.org,
	"Clément Pit--Claudel" <clement.pit@gmail.com>
Subject: bug#25132: 26.0.50; emacs hangs when loading org file with python source blocks
Date: Thu, 19 Jan 2017 19:52:18 -0500	[thread overview]
Message-ID: <878tq6wo1p.fsf@users.sourceforge.net> (raw)
In-Reply-To: <aa494e14-f35a-92c4-b954-c7ba8e4ab4b1@yandex.ru> (Dmitry Gutov's message of "Thu, 19 Jan 2017 19:25:04 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 08.01.2017 00:20, npostavs@users.sourceforge.net wrote:
>> -            (inhibit-modification-hooks t))
>> +            (inhibit-modification-hooks
>> +             (progn (make-local-variable 'inhibit-modification-hooks) t)))
>
> Are we not worried that inhibit-modificaiton-hooks will become
> buffer-local even after control flow leaves this let*?

My feeling is that inhibit-modification-hooks should usually be buffer
local anyway.

> If we are not, why not make inhibit-modification-hooks always
> buffer-local instead?

It would have to be in addition to, because even after doing
(make-variable-buffer-local 'var), (let ((var 'foo))...) still makes a
global binding.  `make-variable-buffer-local' only has effect for
`setq', which I think will hardly ever happen for
`inhibit-modification-hooks'.

Actually, I just grepped for inhibit-modification-hooks and the only
non-let I found is this:

(defun read-passwd (prompt &optional confirm default)
   ...
      (minibuffer-with-setup-hook
          (lambda ()
             ...
             (setq-local inhibit-modification-hooks nil) ;bug#15501.
             ...))
   ...)





  parent reply	other threads:[~2017-01-20  0:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 18:33 bug#25132: 26.0.50; emacs hangs when loading org file with python source blocks David Dynerman
2016-12-08  2:08 ` Glenn Morris
2016-12-08  2:40   ` Clément Pit--Claudel
2016-12-08  7:17     ` David Dynerman
2017-01-07  6:38       ` npostavs
2017-01-07 21:20         ` npostavs
     [not found]         ` <87eg0e36un.fsf@users.sourceforge.net>
2017-01-19 16:25           ` Dmitry Gutov
     [not found]           ` <aa494e14-f35a-92c4-b954-c7ba8e4ab4b1@yandex.ru>
2017-01-20  0:52             ` npostavs [this message]
2017-01-20  2:22               ` Clément Pit--Claudel
2017-01-20  3:18                 ` npostavs
2017-01-23  3:53               ` Dmitry Gutov
2017-01-24  3:36                 ` npostavs
2017-01-29 16:05                   ` npostavs

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=878tq6wo1p.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=25132@debbugs.gnu.org \
    --cc=clement.pit@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=emperordali@block-party.net \
    /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).