all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Handling large files with Emacs
Date: Wed, 24 Oct 2012 20:16:12 +0200	[thread overview]
Message-ID: <83hapjbus3.fsf@gnu.org> (raw)
In-Reply-To: <loom.20121024T112644-629@post.gmane.org>

> From: Tom <adatgyujto@gmail.com>
> Date: Wed, 24 Oct 2012 09:34:41 +0000 (UTC)
> 
> Jambunathan K <kjambunathan <at> 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.

And it isn't a problem, indeed, unless the mode in question does
something pathological with its definition of font-lock-keywords etc.

> 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?

It is, and it does.  But whenever you scroll to another portion in the
buffer, JIT font-lock fontifies the displayed portion before
displaying it, which could slow down redisplay, regardless of stealth.



  reply	other threads:[~2012-10-24 18:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 19:33 Handling large files with Emacs Fab
2012-10-23 19:52 ` Eli Zaretskii
     [not found] ` <mailman.11564.1351021951.855.help-gnu-emacs@gnu.org>
2012-10-23 20:09   ` Fab
2012-10-23 20:40     ` Eli Zaretskii
2012-10-24  7:52       ` Tom
2012-10-24  9:22         ` Jambunathan K
2012-10-24  9:34           ` Tom
2012-10-24 18:16             ` Eli Zaretskii [this message]
2012-10-24  9:40           ` Tom
2012-10-24 13:51             ` Jambunathan K
2012-10-24 18:16             ` Eli Zaretskii
2012-10-24 19:09               ` Tom
2012-10-24 20:12                 ` Ludwig, Mark
     [not found]               ` <mailman.11635.1351105779.855.help-gnu-emacs@gnu.org>
2012-10-24 19:47                 ` Stefan Monnier
     [not found]     ` <mailman.11568.1351024821.855.help-gnu-emacs@gnu.org>
2012-10-23 20:49       ` Fab
2012-10-24 15:29 ` Stefan Monnier
2012-10-24 17:19   ` Fab
2012-10-24 19:32     ` Stefan Monnier
2012-10-24 20:19     ` Drew Adams

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83hapjbus3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.