From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Joseph Garvin <joseph.h.garvin@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Native display of line numbers: visual line-counting
Date: Sun, 25 Jun 2017 16:20:30 -0400 [thread overview]
Message-ID: <jwva84vx1xw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAH=MJ4aeE3cXnCbxxXiJVFQg84_UYT1T_LJqoYA0BXnjGXdKfg@mail.gmail.com> (Joseph Garvin's message of "Sun, 25 Jun 2017 14:31:43 -0500")
> I take it for granted when using emacs that there is some configuration
> work involved. As long as there is a function I can bind for up/down that
> matches the the relative line numbering, it's not super important to me
> that they automatically are synced somehow. FWIW, visual line mode
> automagically rebinds the navigation keys already, so if the relative line
> numbering was just labeling the lines as visual line mode renders them,
> rendering and input should line up.
The problem I was alluding to is that the efficient way for the
redisplay to provide relative visual-line numbers (i.e. working
directly on the matrices) would provide a semantics which I'm not sure
matches faithfully the functions available to Elisp
(e.g. vertical-motion).
So, this argues for the use of the more expensive move_it_* functions to
compute the relative visual-line numbers (IIUC these are also easier to
integrate in the current code, according to Eli).
Stefan
next prev parent reply other threads:[~2017-06-25 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 18:15 Native display of line numbers: visual line-counting Eli Zaretskii
2017-06-24 19:03 ` Joseph Garvin
2017-06-24 19:22 ` Eli Zaretskii
2017-06-24 20:13 ` Joseph Garvin
2017-06-24 20:42 ` James Nguyen
2017-06-25 19:16 ` Stefan Monnier
2017-06-25 19:31 ` Joseph Garvin
2017-06-25 20:20 ` Stefan Monnier [this message]
2017-06-26 2:37 ` Eli Zaretskii
2017-06-26 2:35 ` Eli Zaretskii
[not found] ` <CAEwkUWN-W94hfP1N=QR2A91Ae_bVBbX1xZpzPPuRQ8siMir5oA@mail.gmail.com>
2017-06-27 15:00 ` Eli Zaretskii
2017-06-27 16:26 ` Filipe Silva
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=jwva84vx1xw.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=joseph.h.garvin@gmail.com \
/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.