unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 32848@debbugs.gnu.org, andlind@gmail.com, darkfeline@felesatra.moe
Subject: bug#32848: 26.1; follow-mode cursor move breaks with frame-resize-pixelwise
Date: Sun, 30 Sep 2018 20:00:14 +0300	[thread overview]
Message-ID: <83mury53a9.fsf@gnu.org> (raw)
In-Reply-To: <20180930140921.GD6305@ACM> (message from Alan Mackenzie on Sun,  30 Sep 2018 14:09:21 +0000)

> Date: Sun, 30 Sep 2018 14:09:21 +0000
> Cc: 32848@debbugs.gnu.org, andlind@gmail.com, darkfeline@felesatra.moe
> From: Alan Mackenzie <acm@muc.de>
> 
> The problem was that LH point was "straddling" the window "edge".  The
> solution appears to be to copy what happens when LH point is outside the
> window, i.e. allow redisplay to move it back to the centre of the window.
> 
> For this, a simple (forward-line) suffices.
> 
> The trouble is, all the make-cursor-line-fully-visible stuff we've done
> then becomes redundant, since point will never be left inside a partially
> displayed line, except possibly at EOB.
> 
> Here's my current patch.  What do you think?

I think we should revert the change to set
make-cursor-line-fully-visible locally on the emacs-26 branch, and
install this patch instead.  But on master, I think we need both this
patch and a special function that sets make-cursor-line-fully-visible
nil in non-last windows under follow-mode, because that's definitely
what follow-mode wants.

WDYT?





  reply	other threads:[~2018-09-30 17:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 22:49 bug#32848: 26.1; follow-mode cursor move breaks with frame-resize-pixelwise Allen Li
2018-09-27  6:04 ` Eli Zaretskii
2018-09-27  8:06 ` Eli Zaretskii
2018-09-28 20:31   ` Alan Mackenzie
2018-09-28 21:27     ` Eli Zaretskii
2018-09-29  8:35       ` Alan Mackenzie
2018-09-29 10:26         ` Eli Zaretskii
2018-09-29 11:25           ` Alan Mackenzie
2018-09-29 13:47             ` Eli Zaretskii
2018-09-29 13:56               ` Eli Zaretskii
2018-09-29 14:48               ` Alan Mackenzie
2018-09-29 15:06                 ` Eli Zaretskii
2018-09-29 20:25                   ` Alan Mackenzie
2018-09-30  5:30                     ` Eli Zaretskii
2018-09-30 11:16                       ` Eli Zaretskii
2018-09-30 12:16                         ` Alan Mackenzie
2018-09-30 12:56                           ` Eli Zaretskii
2018-09-30 14:09                             ` Alan Mackenzie
2018-09-30 17:00                               ` Eli Zaretskii [this message]
2018-10-01 12:33                                 ` Alan Mackenzie
2018-10-01 13:47                                   ` Eli Zaretskii
2018-10-15  9:23                                     ` Alan Mackenzie
2018-10-15 15:07                                       ` Eli Zaretskii
2018-10-15 17:26                                         ` Alan Mackenzie
2018-10-15 18:02                                           ` Eli Zaretskii
2018-09-30 11:02   ` Alan Mackenzie
2018-09-30 11:24     ` Eli Zaretskii
2018-09-30 13:55       ` Alan Mackenzie
2018-10-17 10:17   ` Alan Mackenzie

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83mury53a9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=32848@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=andlind@gmail.com \
    --cc=darkfeline@felesatra.moe \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).