From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Vitalie Spinu Newsgroups: gmane.emacs.devel,gmane.emacs.help Subject: Re: trunk r116426: * lisp/jit-lock.el (jit-lock-mode): Keep it disabled in indirect buffers. Date: Wed, 21 May 2014 21:51:29 -0700 Organization: UCLA Anderson School of Management Message-ID: <87k39ee7qm.fsf@gmail.com> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1400734309 13659 80.91.229.3 (22 May 2014 04:51:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 22 May 2014 04:51:49 +0000 (UTC) Cc: help-gnu-emacs@gnu.org, =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 22 06:51:44 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 1WnKyl-0000ps-7e for ged-emacs-devel@m.gmane.org; Thu, 22 May 2014 06:51:43 +0200 Original-Received: from localhost ([::1]:34700 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WnKyk-0008Ai-T3 for ged-emacs-devel@m.gmane.org; Thu, 22 May 2014 00:51:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42123) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WnKyh-0008AP-1x for emacs-devel@gnu.org; Thu, 22 May 2014 00:51:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WnKyg-0008Av-3U for emacs-devel@gnu.org; Thu, 22 May 2014 00:51:39 -0400 Original-Received: from mail-pb0-x231.google.com ([2607:f8b0:400e:c01::231]:56157) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WnKye-0008AM-4W; Thu, 22 May 2014 00:51:36 -0400 Original-Received: by mail-pb0-f49.google.com with SMTP id jt11so2111725pbb.36 for ; Wed, 21 May 2014 21:51:33 -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=Zi0N1fcPdhD1+QAzFk4LRbeMSINfGZHzY8vf5YGaTzc=; b=WJc6KE6K0ndbm4+Wgc9AgJfRttxHPvosOO7LOVtxipS4iTad98oWB68rpFfpjwvvgF 4/GPOm/bpXs+s9543H0EZxbEqVjlefShFLrs/ZdJHo6wa5pm3+HUFQ0a1s3t4ED1JueX 04VMk+1Gmzy1VEpCmFwD/NIRoHuV0GQ//MBF8eHNJAW2SlCr4RdXyW2FiE+ARF3nAocI /M8qn/vj+AgtHVkSG56G80vMA7kz+1YURhdWDqRQIb4qdNKNXBjxYLVwPyJ7Cn8ohu83 RPNHgDijlUUKsGyJ+nh0oQGgq1le6dFCW7vGX80kqYcwceJQrHbclRYc3ID9NpbFZUn+ BIoA== X-Received: by 10.68.247.131 with SMTP id ye3mr977232pbc.40.1400734293271; Wed, 21 May 2014 21:51:33 -0700 (PDT) Original-Received: from localhost ([2607:f010:2e9:2:7218:8bff:feae:a65e]) by mx.google.com with ESMTPSA id qv3sm10742517pbb.87.2014.05.21.21.51.30 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 21 May 2014 21:51:31 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Mon, 07 Apr 2014 16:40:19 -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:400e:c01::231 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:172014 gmane.emacs.help:97788 Archived-At: >>> Stefan Monnier on Mon, 07 Apr 2014 16:40:19 -0400 wrote: >> I don't know anything about fontification techniques, so I don't even >> know if the question makes sense, but isn't there a way to get >> fontification (even if slower than jit-lock-mode) in the indirect >> buffer, and keep the base buffer jit-locked? SM> Everything is possible, yes. But I just recommend you don't go there, SM> it's a waste of time. Waste of time or not, it has been done: https://github.com/vitoshka/polymode Indirect buffers constitute the core of mode switching but are not crucial for the rest of the package. I intentionally abstracted it from all other stuff. If emacs ever comes with something smarter than indirect-buffers I would be happy to adapt the mode switching mechanism. I have been using it for more than an year in an unfinished state for markdown and noweb and the experience was pretty delightful. Indirect buffers are very fast and one-mode-per-indirect-buffer strategy makes the whole system pretty robust. Only recently I found time to finish the design, but then discovered that jit-lock was removed. I am piggybacking on jit-lock and its removal is a real bad luck. The last thing I need right now is to re-implement jit-lock in indirect buffers. Would it be possible to add a binary switch so that people can activate jit-lock if they really need it? Thanks, Vitalie