unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jonas@bernoul.li, 45319@debbugs.gnu.org
Subject: bug#45319: 28.0.50; Redisplay: `forward-char' moves backwards into invisible text
Date: Sun, 20 Dec 2020 03:15:46 +0100	[thread overview]
Message-ID: <87tush2pf1.fsf@web.de> (raw)
In-Reply-To: <83r1nmt08a.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 19 Dec 2020 15:05:25 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> I don't think I understand the problem well enough yet to answer that
> question, especially since you say that your simplified recipe behaves
> differently.
>
> What exactly is the problem in the magit case? does it use the value
> of point in some way, and if so, how?  IOW, what is "section
> highlighting" in magit?

Let me ask a question first, for my better understanding, I'm curious:
what's your opinion about the (in my eyes) wrong value of point present
when `post-command-hook' is run?  Is it (1) expected and totally makes
sense, should be like that, or more like (2) not relevant, should not be
relied on, or (3) makes not much sense and is not so good but hard to
get to grips?

> A stab in the dark: there's disable-point-adjustment, which could be
> set temporarily, perhaps that could help?

Would that help to fix the behavior of `hl-line-mode' marking the wrong
line?

The Magit case is not much different.  Here a "section" is simply not a
line but a set of consecutive lines denoting a commit (headline + diff,
for example).  As with hl-line-mode, the wrong section is highlighted
when moving.  But since some commands depend on the currently
highlighted section, the consequence is that these commands then operate
on the wrong section.


Regards,

Michael.





  reply	other threads:[~2020-12-20  2:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19  6:10 bug#45319: 28.0.50; Redisplay: `forward-char' moves backwards into invisible text Michael Heerdegen
2020-12-19  9:10 ` Eli Zaretskii
2020-12-19 11:21   ` Michael Heerdegen
2020-12-19 11:26     ` Eli Zaretskii
2020-12-19 12:09       ` Michael Heerdegen
2020-12-19 12:19         ` Eli Zaretskii
2020-12-19 12:44           ` Michael Heerdegen
2020-12-19 13:05             ` Eli Zaretskii
2020-12-20  2:15               ` Michael Heerdegen [this message]
2020-12-20  3:32               ` Michael Heerdegen
2020-12-20  8:01               ` Michael Heerdegen
2020-12-20 15:38                 ` 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

  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=87tush2pf1.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=45319@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jonas@bernoul.li \
    /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).