From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: relative line numbers and folding: how to make they play along?
Date: Fri, 15 Jul 2016 10:07:52 +0300 [thread overview]
Message-ID: <83mvlj7513.fsf@gnu.org> (raw)
In-Reply-To: <jwvr3aw0wa7.fsf-monnier+gmane.emacs.help@gnu.org> (message from Stefan Monnier on Thu, 14 Jul 2016 17:03:07 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Thu, 14 Jul 2016 17:03:07 -0400
>
> >> Actually, I don't think there needs to be flickering if the first step
> >> ("perform redisplay of window") just computes the new matrices without
> >> performing any drawing.
> > Since the display engine computes the number of each screen line as it
> > lays them out, I don't understand why would 2 phases be needed. I'm
> > probably missing something.
>
> If we bake it into the redisplay code, we can indeed do it "on the fly",
> but if we want this feature to be implemented in Elisp it seems a lot
> more tricky to avoid the 2 passes.
But this sub-thread started with you talking about baking it into
redisplay:
> I think to implement relative-visual-linum-mode efficiently, we'd need
> help from the display engine. E.g.:
> - First perform redisplay of the window.
> - then, go through the window, visual-line by visual-line
> and add something in the margin.
> - then update the margin part of the matrices.
These two passes are described in terms of what redisplay does, they
are not visible to Lisp: we don't return to the command loop after
each window's redisplay, and the glyph matrices are not exposed to
Lisp, either.
So now I'm confused about what you are suggesting.
next prev parent reply other threads:[~2016-07-15 7:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 15:11 relative line numbers and folding: how to make they play along? Filipe Silva
2016-07-12 4:51 ` Eli Zaretskii
2016-07-13 3:43 ` Filipe Silva
2016-07-13 20:10 ` Stefan Monnier
2016-07-13 20:23 ` Eli Zaretskii
2016-07-13 22:33 ` Filipe Silva
2016-07-14 15:02 ` Eli Zaretskii
[not found] ` <mailman.1359.1468449224.26859.help-gnu-emacs@gnu.org>
2016-07-14 1:29 ` Dan Espen
2016-07-14 2:36 ` Stefan Monnier
2016-07-14 15:06 ` Eli Zaretskii
2016-07-14 15:55 ` Filipe Silva
2016-07-14 15:58 ` Filipe Silva
2016-07-14 16:12 ` Eli Zaretskii
2016-07-14 16:51 ` Filipe Silva
2016-07-14 18:23 ` Boris
2016-07-14 21:03 ` Stefan Monnier
2016-07-15 0:04 ` Filipe Silva
2016-07-15 0:18 ` Stefan Monnier
2016-07-15 0:41 ` Filipe
2016-07-15 7:07 ` Eli Zaretskii [this message]
2016-07-15 13:53 ` Stefan Monnier
2016-07-15 14:22 ` Eli Zaretskii
2016-07-15 14:54 ` Stefan Monnier
2016-07-15 15:34 ` Filipe Silva
[not found] ` <mailman.1414.1468511758.26859.help-gnu-emacs@gnu.org>
2016-07-15 2:02 ` Dan Espen
[not found] ` <mailman.1374.1468463825.26859.help-gnu-emacs@gnu.org>
2016-07-14 3:20 ` Rusi
2016-07-14 12:17 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mvlj7513.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.