From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 14616@debbugs.gnu.org
Subject: bug#14616: 24.3.50; Excessive cursor movement on non-X Emacs
Date: Fri, 02 Aug 2013 18:07:43 +0300 [thread overview]
Message-ID: <838v0kyvuo.fsf@gnu.org> (raw)
In-Reply-To: <m338qsz07w.fsf@stories.gnus.org>
> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Cc: 14616@debbugs.gnu.org
> Date: Fri, 02 Aug 2013 15:33:23 +0200
>
> Breakpoint 6, cursor_to (f=0xb7fbe0, vpos=11, hpos=0) at terminal.c:113
> 113 if (FRAME_TERMINAL (f)->cursor_to_hook)
> #0 cursor_to (f=0xb7fbe0, vpos=11, hpos=0) at terminal.c:113
> #1 0x000000000041aeeb in update_frame_1 (inhibit_id_p=<optimized out>,
> force_p=<optimized out>, f=0xb7fbe0) at dispnew.c:4606
>
> Lisp Backtrace:
> "redisplay_internal (C function)" (0xb5b5a8)
> "delete-process" (0xffffd950)
> "let" (0xffffda98)
> "while" (0xffffdb88)
> "let" (0xffffdcd8)
> "eval" (0xffffddf8)
> "eval-last-sexp-1" (0xffffdf80)
> "eval-last-sexp" (0xffffe148)
> "call-interactively" (0xffffe2f0)
> "command-execute" (0xffffe418)
This is normal: Emacs is setting the cursor one last time after it
finishes updating the frame. And redisplay is triggered by
delete-process.
next prev parent reply other threads:[~2013-08-02 15:07 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
2013-08-01 16:46 ` Eli Zaretskii
2013-08-02 13:33 ` Lars Magne Ingebrigtsen
2013-08-02 15:07 ` Eli Zaretskii [this message]
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
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=838v0kyvuo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14616@debbugs.gnu.org \
--cc=larsi@gnus.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 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).