From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Vitalie Spinu Newsgroups: gmane.emacs.devel Subject: Re: trunk r116426: * lisp/jit-lock.el (jit-lock-mode): Keep it disabled in indirect buffers. Date: Fri, 30 May 2014 12:26:57 -0700 Organization: UCLA Anderson School of Management Message-ID: <874n07rrsu.fsf@gmail.com> References: <87k39ee7qm.fsf@gmail.com> <87ioowcr7l.fsf@gmail.com> <8738g0ccig.fsf@gmail.com> <87d2f3y0f8.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1401478035 12502 80.91.229.3 (30 May 2014 19:27:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 30 May 2014 19:27:15 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 30 21:27:08 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WqSSK-0003gA-DC for ged-emacs-devel@m.gmane.org; Fri, 30 May 2014 21:27:08 +0200 Original-Received: from localhost ([::1]:56207 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WqSSJ-0001eX-TZ for ged-emacs-devel@m.gmane.org; Fri, 30 May 2014 15:27:07 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41326) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WqSSG-0001bP-1p for emacs-devel@gnu.org; Fri, 30 May 2014 15:27:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WqSSF-0004js-8m for emacs-devel@gnu.org; Fri, 30 May 2014 15:27:04 -0400 Original-Received: from mail-ie0-x22e.google.com ([2607:f8b0:4001:c03::22e]:62514) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WqSSF-0004jF-3y for emacs-devel@gnu.org; Fri, 30 May 2014 15:27:03 -0400 Original-Received: by mail-ie0-f174.google.com with SMTP id lx4so2205127iec.33 for ; Fri, 30 May 2014 12:27:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:organization:references:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=BYuj2MAYM1f5p8pkxlaRZXmFCBSb61mlLA0dUEMPmKo=; b=uZjBzuqNAx/K8b1H1IYY8wif8oDuw3JaFJ8DD48MhKigFFBUX51IcBiUW486nx1U66 bAmfWOuCf6VhL+8a6kBzX5yZhfSP1h2+vdyZFpbo1GMeJjpBfbxpdiBqs7nFojYodQVh Sh85I15+NZLqTqBKdxO0aTvbXFLlmJuAHuYZRxvO9cp7PwVQy/VBtJUMZ9YHJYYhZcrr VeOnGfddyBi6kPYxVrYx3mRIdFf12YiXtwLQ17Aa0lesIKv3Yzd5gp/9qpdEV668idXb SA5mqqGGMw0JipT8XgtXDkeeBYwjcrvj9QVKjRGq4VJPVkW8LTkCgEDx/ng7nMpghszf YdRg== X-Received: by 10.43.84.67 with SMTP id aj3mr18000622icc.38.1401478021537; Fri, 30 May 2014 12:27:01 -0700 (PDT) Original-Received: from localhost ([2602:306:cf9d:36e0:7218:8bff:feae:a65e]) by mx.google.com with ESMTPSA id qn9sm7555727igb.5.2014.05.30.12.26.58 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 30 May 2014 12:27:00 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Sat, 24 May 2014 10:35:11 -0400") User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4001:c03::22e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:172199 Archived-At: >>> Stefan Monnier on Sat, 24 May 2014 10:35:11 -0400 wrote: >> If the patch that you propose is ever implemented, local hooks will >> still be run in current buffer, right? > No, my intention is to only run the hooks in the base buffer. How about running the hooks in all buffers but defining a local version of the hook as a list with explicit indicator of where to run the hook? For example (xxx :current), (xxx :base), (xxx :indirect-when-current). Then jit-lock-after-change could be declared as (jit-lock-after-change :base). [...] >> Coming back to the original jit-lock problem. I still have no clue how >> to fix it without copying the whole initialization part of jit-lock into >> polymode. > Enable font-lock in the base buffer (and only there) using polymode's > font-lock rules (which will dispatch to the appropriate indirect buffer). This would work if your idea is implemented, e.g. change-functions are executed in the base buffer. Currently, modifications of indirect buffers don't trigger font-lock at all. I have activated font-lock in the indirect buffers by copy-pasting the jit-lock-mode code. It works, but I am noticing occasional emacs crashes on backward-delete-char-untabify and kill-word which don't occur in emacs 24.3. Vitalie