From: hector <hectorlahoz@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs coding modes need 'Suspend Disbelief' button
Date: Fri, 19 May 2017 13:45:10 +0200 [thread overview]
Message-ID: <20170519114510.GA4792@workstation> (raw)
In-Reply-To: <CALyZvKzyfer+sqHGuUEyz05pi_Q4aQnJk0=F6-06KvVaw2=_9g@mail.gmail.com>
On Fri, May 19, 2017 at 10:54:28AM +0000, Jason Vas Dias wrote:
> The insistence of modern emacs on always unconditionally
> syntax checking everything greatly slows down typing and
> is a major inhibition to quick editing of large source files .
Maybe disabling fontification is enough. You can do it for large
buffers with "font-lock-maximum-size".
Or setting the variable "font-lock-maximum-decoration".
I'm not sure whether this would disable parsing.
next prev parent reply other threads:[~2017-05-19 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 10:54 emacs coding modes need 'Suspend Disbelief' button Jason Vas Dias
2017-05-19 11:20 ` tomas
[not found] ` <CALyZvKzvUBe1-+yTnpK97MA=Dh5q89RmTugG3CJ0bcrbqnd2Eg@mail.gmail.com>
2017-05-19 11:37 ` Fwd: " Jason Vas Dias
2017-05-20 7:47 ` Robert Thorpe
2017-05-19 11:42 ` Óscar Fuentes
2017-05-19 11:45 ` hector [this message]
2017-05-19 13:35 ` Drew Adams
2017-05-19 16:23 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170519114510.GA4792@workstation \
--to=hectorlahoz@gmail.com \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).