unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: amaikinono@gmail.com
Cc: 44448@debbugs.gnu.org
Subject: bug#44448: Fwd: bug#44448:
Date: Thu, 12 Aug 2021 17:07:06 +0300	[thread overview]
Message-ID: <83mtpmdaet.fsf@gnu.org> (raw)
In-Reply-To: <83wnoqde8d.fsf@gnu.org> (message from Eli Zaretskii on Thu, 12 Aug 2021 15:44:34 +0300)

> Date: Thu, 12 Aug 2021 15:44:34 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 44448@debbugs.gnu.org
> 
> Thanks.  I see the cause of it: it's the :eval forms that we execute
> when we redisplay the mode line, as part of redisplaying a window.
> When more than one window displays the same buffer at different buffer
> positions, when Emacs redisplays a non-selected window, it temporarily
> moves point to the place where it is displayed in that non-selected
> window.  If C-g is processed while those :eval forms run, with the
> buffer's point temporarily moved, you will see point in the selected
> window "inherit" the position of point from the other window showing
> the same buffer.  As evidence, after this happens, you should be able
> to see this in *Messages*:
> 
>   Error during redisplay: (mode-line-default-help-echo #<window 3 on paren.el>) signaled (quit)

Actually, that cannot be the whole story.  Because evaluating the
:eval forms in the mode line arranges for catching the errors (and the
above text in *Messages* is the evidence that it works here), and so
we should have still run redisplay_window to completion after that,
which includes restoring the buffer's point to its original value.
Hmm...





  reply	other threads:[~2021-08-12 14:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 16:48 bug#44448: 27.1; Strange inteference between timer, modeline/header-line and buffer position in window Amai Kinono
2020-11-04 20:12 ` Eli Zaretskii
2020-12-07 16:45   ` Lars Ingebrigtsen
2021-02-05 13:42 ` bug#44448: Amai Kinono
2021-02-05 13:44   ` bug#44448: Lars Ingebrigtsen
2021-08-11  5:49 ` bug#44448: Amai Kinono
2021-08-11 11:20   ` bug#44448: Lars Ingebrigtsen
     [not found]     ` <CAPu3fz0cn0NjjSdZ34KYCw0ZweaR3tBCaRTxwe3fccTQL=Gq5g@mail.gmail.com>
2021-08-11 12:18       ` bug#44448: Fwd: bug#44448: Amai Kinono
2021-08-11 11:43   ` bug#44448: Eli Zaretskii
     [not found]     ` <CAPu3fz1HwaXCztR05vjXO19_6oWXOPgG7LKV2t7isV6J9KMMCQ@mail.gmail.com>
2021-08-11 12:18       ` bug#44448: Fwd: bug#44448: Amai Kinono
2021-08-12 12:44         ` Eli Zaretskii
2021-08-12 14:07           ` Eli Zaretskii [this message]
     [not found]           ` <CAPu3fz1YHXqAdN+0B-45J+geEwC70QTuAZLe1vuwmq+gTq64NA@mail.gmail.com>
2021-08-13  9:49             ` bug#44448: Fwd: " Amai Kinono
2021-08-14  9:25             ` Eli Zaretskii
2021-08-15 11:21               ` Eli Zaretskii
2021-08-15 12:12                 ` Amai Kinono
2021-08-15 14:15                   ` Eli Zaretskii
2021-08-15 18:10                     ` Amai Kinono
2021-08-15 18:29                       ` Eli Zaretskii
2021-08-16 18:28                         ` Amai Kinono
2021-08-16 19:09                           ` Eli Zaretskii
2021-08-17 18:09                             ` Amai Kinono
2021-08-17 18:31                               ` Eli Zaretskii
2021-08-18 12:05                                 ` Amai Kinono
2021-08-18 13:16                                   ` Eli Zaretskii
2021-08-18 14:00                                     ` Amai Kinono
2021-08-18 15:47                                       ` Eli Zaretskii
2021-12-04  6:13                                         ` Amai Kinono
2021-12-04  8:38                                           ` Eli Zaretskii
2021-12-04 11:42                                             ` Amai Kinono
2021-12-04 16:07                                               ` Eli Zaretskii
2021-08-11 12:22 ` bug#44448: [Amai Kinono] bug#44448: Lars Ingebrigtsen

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=83mtpmdaet.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44448@debbugs.gnu.org \
    --cc=amaikinono@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 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).