From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 12867@debbugs.gnu.org
Subject: bug#12867: 24.3.50; easy-to-repro crash involving mode line
Date: Tue, 13 Nov 2012 14:52:54 +0200 [thread overview]
Message-ID: <83sj8dvf4p.fsf@gnu.org> (raw)
In-Reply-To: <50A2033C.6070504@gmx.at>
> Date: Tue, 13 Nov 2012 09:22:20 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: Eli Zaretskii <eliz@gnu.org>, 12867@debbugs.gnu.org
>
> > FWIW, I recently added such a cache (in Elisp) to nlinum.el, and on my
> > test case (largish file with C-v/M-v style scrolling) the difference was
> > very significant (but the previous code had no cache at all, not even
> > base_line_pos).
>
> So we now already have a syntax-ppss cache and a nlinum cache. Couldn't
> we maintain one cache per buffer, updated by one and the same algorithm?
These two cache different information, so making such a cache
efficient is not very trivial.
At least for nlinum, if it were to use some Lisp binding of
find_next_newline_no_quit (there's no such binding at this time, but
it wouldn't be hard to provide one), they could use a newline cache
provided by region-cache.c for free.
next prev parent reply other threads:[~2012-11-13 12:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 3:52 bug#12867: 24.3.50; easy-to-repro crash involving mode line Drew Adams
2012-11-12 15:40 ` Eli Zaretskii
2012-11-12 17:09 ` Drew Adams
2012-11-12 17:52 ` Eli Zaretskii
2012-11-12 18:16 ` Drew Adams
2012-11-12 18:35 ` Eli Zaretskii
2012-11-12 19:07 ` bug#12872: " Drew Adams
2012-11-12 17:31 ` martin rudalics
2012-11-12 18:19 ` Eli Zaretskii
2012-11-12 20:55 ` Stefan Monnier
2012-11-13 8:22 ` martin rudalics
2012-11-13 12:52 ` Eli Zaretskii [this message]
2012-11-13 13:50 ` martin rudalics
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=83sj8dvf4p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12867@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.