From: "Drew Adams" <drew.adams@oracle.com>
To: "'Fab'" <fab4100@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: Handling large files with Emacs
Date: Wed, 24 Oct 2012 13:19:29 -0700 [thread overview]
Message-ID: <6A4BA8A28EAB4E0683A70F50BFE37E48@us.oracle.com> (raw)
In-Reply-To: <87wqyfzt26.fsf@panzer.v.cablecom.net>
> It actually was all my mistake and I was not aware the
> linum.el caused all the trouble!
Maybe linum should (by default) let users know when they might incur a
performance penalty because the buffer is large. Maybe we should have a user
option that specifies a size limit beyond which linum would avert you of the
potential slowdown, or even (optionally) turn itself off.
That's what we did for font-locking, for instance (option
`font-lock-maximum-size'), before just-in-time font-locking was available.
IOW, maybe we should not be too quick to just ascribe this to user error. Maybe
linum could be more helpful to users.
prev parent reply other threads:[~2012-10-24 20:19 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
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 [this message]
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=6A4BA8A28EAB4E0683A70F50BFE37E48@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=fab4100@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.
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.