From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tom Newsgroups: gmane.emacs.help Subject: Re: Handling large files with Emacs Date: Wed, 24 Oct 2012 09:34:41 +0000 (UTC) Message-ID: References: <87k3uhf0gc.fsf@panzer.v.cablecom.net> <87a9vdeyrf.fsf@panzer.v.cablecom.net> <83objsc47x.fsf@gnu.org> <876260cji8.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1351071312 30002 80.91.229.3 (24 Oct 2012 09:35:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 24 Oct 2012 09:35:12 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Oct 24 11:35:21 2012 Return-path: Envelope-to: geh-help-gnu-emacs@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 1TQxMs-0006OG-AA for geh-help-gnu-emacs@m.gmane.org; Wed, 24 Oct 2012 11:35:18 +0200 Original-Received: from localhost ([::1]:56772 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TQxMk-0006sQ-J6 for geh-help-gnu-emacs@m.gmane.org; Wed, 24 Oct 2012 05:35:10 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:44827) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TQxMV-0006cd-SW for help-gnu-emacs@gnu.org; Wed, 24 Oct 2012 05:35:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TQxMT-0001lW-He for help-gnu-emacs@gnu.org; Wed, 24 Oct 2012 05:34:55 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:42013) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TQxMT-0001kS-BI for help-gnu-emacs@gnu.org; Wed, 24 Oct 2012 05:34:53 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TQxMZ-0006Av-0i for help-gnu-emacs@gnu.org; Wed, 24 Oct 2012 11:34:59 +0200 Original-Received: from 188-143-25-41.pool.digikabel.hu ([188.143.25.41]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 Oct 2012 11:34:59 +0200 Original-Received: from adatgyujto by 188-143-25-41.pool.digikabel.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 Oct 2012 11:34:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 21 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 188.143.25.41 (Opera/9.80 (Windows NT 6.1; U; IBM EVV/3.0/EAK01AG9/LE; en) Presto/2.10.289 Version/12.02) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:87390 Archived-At: Jambunathan K gmail.com> writes: > > > > I think it's because syntax highlight or something. When I try opening > > SQL dumps (say, 200MB) then Emacs grinds to a halt for a minute or > > so, and moving in the file is very slow even after that. > > Have you experimented with `font-lock-maximum-size' together with > `font-lock-support-mode'? > Not yet, because I rarely need this and if I do then it's simpler to open the file in fundamental mode. But the real question is if font locking is really the cuplrit then why do we need to resort such special settings? We have fast enough computers and AFAIK jit font-lock is the default, so it should not be a problem. Even if lisp perfomance cannot be improved much, font lock should be clever enough to stay in the background and do stealth fontification on remote parts of the large buffer only if the user is idle and only in chunks, so it can yield to user input. Isn't this what JIT font-lock is supposed to do in the first place?