From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: The future of Follow Mode - a proposal.
Date: Wed, 24 Feb 2016 19:30:55 -0500 [thread overview]
Message-ID: <jwvvb5diqnh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <834mcxhnaq.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 24 Feb 2016 22:21:33 +0200")
> The most striking one is vertical-motion (which doesn't belong to
> redisplay at all, and thus will not benefit from your suggestion).
> Redisplay proper does similar stuff at places as part of its decision
> where to place point and whether/by how much to scroll the window in
> order to bring point back into view.
I see, thanks. Indeed both examples fall outside the scope of
"redisplay" that could be covered by the kind of hook I have in mind.
I live in a world where wrapped lines are sufficiently rare that I don't
really care and rarely think about what can happen in those cases.
But now that I think about it: I'm not sure how vertical-motion could
handle a "multiple-window" case where the windows don't have the same
width (same thing in other similar cases, such as with overlays with
a `window' property that make them only apply to some of the multiple
windows, or when the windows aren't all in the same frame and don't use
the same font). The desired semantic seems undefined except for the
case where the vertical motion is applied to the "currently displayed
state" (so we know when to use which window data).
Stefan
next prev parent reply other threads:[~2016-02-25 0:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 19:56 The future of Follow Mode - a proposal Alan Mackenzie
2016-02-18 20:24 ` Eli Zaretskii
2016-02-19 14:25 ` Alan Mackenzie
2016-02-19 14:34 ` martin rudalics
2016-02-19 16:12 ` Eli Zaretskii
2016-02-19 16:08 ` Eli Zaretskii
2016-02-19 18:18 ` Alan Mackenzie
2016-02-19 18:45 ` Eli Zaretskii
2016-02-20 12:44 ` Alan Mackenzie
2016-02-20 13:05 ` Eli Zaretskii
2016-02-23 23:11 ` Alan Mackenzie
2016-02-24 3:57 ` Stefan Monnier
2016-02-24 17:14 ` Eli Zaretskii
2016-02-24 18:57 ` Stefan Monnier
2016-02-24 19:19 ` Eli Zaretskii
2016-02-24 20:10 ` Stefan Monnier
2016-02-24 20:21 ` Eli Zaretskii
2016-02-25 0:30 ` Stefan Monnier [this message]
2016-02-25 16:28 ` Eli Zaretskii
2016-02-25 16:46 ` Stefan Monnier
2016-02-25 17:29 ` Eli Zaretskii
2016-02-25 20:30 ` Alan Mackenzie
2016-02-25 20:57 ` Alan Mackenzie
2016-02-25 21:10 ` Stefan Monnier
2016-02-25 22:17 ` Alan Mackenzie
2016-02-28 16:40 ` Stefan Monnier
2016-02-24 18:34 ` Eli Zaretskii
2016-02-25 20:18 ` Alan Mackenzie
2016-02-19 14:56 ` Anders Lindgren
2016-02-19 16:30 ` Eli Zaretskii
2016-02-19 18:45 ` Alan Mackenzie
2016-02-18 20:41 ` John Yates
2016-02-19 16:21 ` Alan Mackenzie
2016-02-19 16:32 ` Eli Zaretskii
2016-02-19 19:25 ` John Yates
2016-02-19 20:27 ` Eli Zaretskii
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=jwvvb5diqnh.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.