From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: Aborting display. Is this possible? Date: Wed, 22 Oct 2014 13:28:04 -0500 Message-ID: <85bnp4arij.fsf@stephe-leake.org> References: <20141019141712.GB3197@acm.acm> <83lhoccdv7.fsf@gnu.org> <20141019154255.GC3197@acm.acm> <83egu4c4om.fsf@gnu.org> <20141020110949.GA2947@acm.acm> <8338aidbcq.fsf@gnu.org> <20141020185757.GD2947@acm.acm> <83lhoabl2x.fsf@gnu.org> <20141020210819.GE2947@acm.acm> <87y4s9rgi9.fsf@fencepost.gnu.org> <83zjcpa11g.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1414002522 22176 80.91.229.3 (22 Oct 2014 18:28:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 22 Oct 2014 18:28:42 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 22 20:28:35 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 1Xh0eA-0006LO-Is for ged-emacs-devel@m.gmane.org; Wed, 22 Oct 2014 20:28:34 +0200 Original-Received: from localhost ([::1]:59780 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xh0eA-0005R6-6s for ged-emacs-devel@m.gmane.org; Wed, 22 Oct 2014 14:28:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57709) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xh0dr-0005Nq-J5 for emacs-devel@gnu.org; Wed, 22 Oct 2014 14:28:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xh0dl-0007oh-8C for emacs-devel@gnu.org; Wed, 22 Oct 2014 14:28:15 -0400 Original-Received: from dnvrco-outbound-snat.email.rr.com ([107.14.73.225]:14557 helo=dnvrco-oedge-vip.email.rr.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xh0dl-0007nt-34 for emacs-devel@gnu.org; Wed, 22 Oct 2014 14:28:09 -0400 Original-Received: from [70.94.38.149] ([70.94.38.149:52260] helo=TAKVER) by dnvrco-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id BE/A6-01272-537F7445; Wed, 22 Oct 2014 18:28:06 +0000 In-Reply-To: (Stefan Monnier's message of "Tue, 21 Oct 2014 12:27:51 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.94 (windows-nt) X-RR-Connecting-IP: 107.14.64.130:25 X-Authority-Analysis: v=2.1 cv=Kc5csGoD c=1 sm=1 tr=0 a=AppmJ/7ZOOFWL/q6u6u93g==:117 a=AppmJ/7ZOOFWL/q6u6u93g==:17 a=ayC55rCoAAAA:8 a=fNEgcOh0sVsA:10 a=o_R75loqY_IA:10 a=9i_RQKNPAAAA:8 a=4BDTsELXTk7gGYxu1oQA:9 X-Cloudmark-Score: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 107.14.73.225 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:175696 Archived-At: Stefan Monnier writes: > There's some general pressure to improve font-locking by making it more > precise, with somewhat marginal improvements but fairly high > processing costs (pushed to the extreme, this involves passing the text > to an external toolchain that parses and type-checks and returns to > Emacs the precise highlighting info; see for example agda-mode). Did you mean "ada-mode" here? I don't find 'agda-mode' in 24.3.94 or ELPA. I'm still having trouble with process communication, so I'll be trying the new FFI mechanism next. But your point is valid; I much prefer faster font-lock, rather than less precise font-lock. I'm not sure my customers really agree; they have not spoken up (other than one complaint that it's too slow on huge files). > So, maybe we're looking at a future where we'll need to provide some way > for delayed/asynchronous font-lock refinement. Ah, like a jpeg sent over a slow internet connection (at least, that's they way I remember it; haven't run into that in years). Perhaps it would be possible to define a subset of the full grammar, that provides some meaningful level of font-lock, and is significantly faster to parse. That would be a lot of work, but I may have to try that if all else fails. -- -- Stephe