From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14616@debbugs.gnu.org
Subject: bug#14616: 24.3.50; Excessive cursor movement on non-X Emacs
Date: Thu, 01 Aug 2013 12:41:29 +0200 [thread overview]
Message-ID: <m3bo5hhew6.fsf@stories.gnus.org> (raw)
In-Reply-To: <83fvuuws3k.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 31 Jul 2013 20:34:55 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> It doesn't actually redraw the lines, at least not on my system. What
> it does is examine each screen line in the 'desired' glyph matrix (a
> structure that describes what _should_ be on the screen) with the
> corresponding line in the 'current' glyph matrix (which describes what
> _is_ on the screen).
I see. Is there a better place to put the trace so that it'll only
trigger when something is actually redrawn? That would make poking
around trying to trigger the bug easier...
> Do you see on your system any writes to the terminal, e.g., in strace?
I tried stracing it now, but couldn't see anything to indicate that it
actually writes anything to the terminal.
> (If you wonder why each iteration through your recipe causes Emacs to
> enter redisplay, then this is caused by delete-process: you will see
> that it calls redisplay_preserve_echo_area, which enters redisplay.
> Presumably, this is because deleting a process or a network connection
> constitutes a status change, and we always call redisplay in that
> case, I think for sentinels' sake. So this is normal, or at least not
> a regression.)
Right.
--
(domestic pets only, the antidote for overdose, milk.)
No Gnus T-Shirt for sale: http://ingebrigtsen.no/no.php
next prev parent reply other threads:[~2013-08-01 10:41 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 8:00 bug#14616: 24.3.50; Excessive cursor movement on non-X Emacs Lars Magne Ingebrigtsen
2013-06-14 8:05 ` Lars Magne Ingebrigtsen
2013-06-23 17:27 ` Eli Zaretskii
2013-06-25 20:18 ` Lars Magne Ingebrigtsen
2013-06-26 16:32 ` Eli Zaretskii
2013-07-19 15:31 ` Lars Magne Ingebrigtsen
2013-07-19 18:46 ` Eli Zaretskii
2013-07-30 14:47 ` Lars Magne Ingebrigtsen
2013-07-30 16:44 ` Eli Zaretskii
2013-07-31 10:03 ` Lars Magne Ingebrigtsen
2013-07-31 10:11 ` Lars Magne Ingebrigtsen
2013-07-31 17:34 ` Eli Zaretskii
2013-08-01 10:41 ` Lars Magne Ingebrigtsen [this message]
2013-08-01 16:46 ` Eli Zaretskii
2013-08-02 13:33 ` Lars Magne Ingebrigtsen
2013-08-02 15:07 ` Eli Zaretskii
2013-08-02 13:46 ` Lars Magne Ingebrigtsen
2013-08-02 14:28 ` Eli Zaretskii
2013-08-03 13:00 ` Lars Magne Ingebrigtsen
2013-08-03 13:32 ` Eli Zaretskii
2013-08-05 18:22 ` Lars Magne Ingebrigtsen
2013-08-05 18:45 ` Eli Zaretskii
2013-08-05 19:10 ` Lars Magne Ingebrigtsen
2013-08-05 19:15 ` Lars Magne Ingebrigtsen
2013-08-05 19:21 ` Lars Magne Ingebrigtsen
2013-08-05 19:45 ` Eli Zaretskii
2013-08-05 19:53 ` Lars Magne Ingebrigtsen
2013-08-06 15:45 ` Eli Zaretskii
2013-08-05 19:40 ` Eli Zaretskii
2013-08-05 19:46 ` Lars Magne Ingebrigtsen
2013-08-05 19:51 ` Lars Magne Ingebrigtsen
2013-08-05 20:10 ` Eli Zaretskii
2013-08-05 20:20 ` Lars Magne Ingebrigtsen
2013-08-06 15:26 ` Eli Zaretskii
2013-08-06 20:32 ` Lars Magne Ingebrigtsen
2013-08-07 13:51 ` Eli Zaretskii
2013-08-02 14:00 ` Lars Magne Ingebrigtsen
2013-08-03 7:57 ` Eli Zaretskii
2013-08-03 13:00 ` Lars Magne Ingebrigtsen
2013-06-14 8:59 ` Eli Zaretskii
2013-06-18 5:22 ` lee
2013-06-18 15:57 ` Eli Zaretskii
2013-06-19 1:38 ` lee
2013-06-27 11:16 ` lee
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=m3bo5hhew6.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=14616@debbugs.gnu.org \
--cc=eliz@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.