all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 51f0ccc: Put follow-mode's engine on pre-redisplay-hook instead of post-command-hook
Date: Wed, 03 Oct 2018 09:52:08 -0400	[thread overview]
Message-ID: <jwvtvm3uoov.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 20181003131411.GB16238@ACM

>> > +;; The magic little box. This function was formerly called after every
>> > +;; command.  It is now called before each redisplay operation (see
>> > +;; `follow-pre-redisplay-function' above), and at the end of several
>> > +;; search/replace commands.  It retains its historical name.
>> I wonder why this is still needed.
> There are interfaces like `isearch-update-post-hook' that need a
> function with no arguments.  Isearch calls this hook at the end of a
> search operation, and this allows follow-mode to resynchronise the
> windows before a redisplay.
>
> I tried removing this interface, hoping that the pre-redisplay-function
> would do everything properly anyway, but it didn't - a search caused the
> LH window to scroll rather than moving point to the RH window.  Also the
> windows have to be aligned before lazy highlighting takes place.  So
> `isearch-update-post-hook' and friends stay.

Thanks.  A comment explaining why these hooks are still used would be very
welcome (apparently, we don't know the deep reason why, but you can
mention the known test cases where it was found to be needed (e.g. what
you just wrote)).


        Stefan




      reply	other threads:[~2018-10-03 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181003105358.19923.64797@vcs0.savannah.gnu.org>
     [not found] ` <20181003105359.AA7EC204E8@vcs0.savannah.gnu.org>
2018-10-03 12:20   ` [Emacs-diffs] master 51f0ccc: Put follow-mode's engine on pre-redisplay-hook instead of post-command-hook Stefan Monnier
2018-10-03 13:14     ` Alan Mackenzie
2018-10-03 13:52       ` Stefan Monnier [this message]

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=jwvtvm3uoov.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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.