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: Mon, 12 Nov 2012 20:19:01 +0200 [thread overview]
Message-ID: <83bof2wup6.fsf@gnu.org> (raw)
In-Reply-To: <50A13289.4050301@gmx.at>
> Date: Mon, 12 Nov 2012 18:31:53 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: Drew Adams <drew.adams@oracle.com>, 12867@debbugs.gnu.org
>
> > The need to redisplay the mode line on every move of point is a killer
> > of many redisplay optimizations. It is also potentially expensive by
> > itself, because it requires Emacs to count lines, something that is
> > not an easy operation in Emacs, which sees the buffer text as a linear
> > array of characters, not a series of lines. So the display engine
> > tries very hard to avoid redisplaying the mode line if it decides that
> > the line number does not need to appear.
>
> I think it would make sense to use a cache for maintaining line numbers.
We already do, but maybe not as extensively as you may have in mind.
See the base_line_pos member of 'struct window'.
There's also region-cache.c, which we could use for that. But before
we do, Someone(TM) should time the thing and see if it's worth our
while to make that cache.
next prev parent reply other threads:[~2012-11-12 18:19 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 [this message]
2012-11-12 20:55 ` Stefan Monnier
2012-11-13 8:22 ` martin rudalics
2012-11-13 12:52 ` Eli Zaretskii
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=83bof2wup6.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.