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: Mon, 05 Aug 2013 21:45:54 +0300 [thread overview]
Message-ID: <83fvuovuvx.fsf@gnu.org> (raw)
In-Reply-To: <m3pptsgfqe.fsf@stories.gnus.org>
> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Cc: bug-gnu-emacs@gnu.org
> Date: Mon, 05 Aug 2013 20:22:17 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > This all sounds depressingly similar to what we found in bug #13864,
> > which was supposed to be fixed long ago. Please use the technique
> > described in http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13864#68 to
> > find out what code sets the frame's garbaged flag. (The line numbers
> > cited in that message are different now, so be sure to use the current
> > ones.)
>
> Ok, I've tried to reproduce this, and a trace is included below.
>
> > Does the recipe you use involve more than one frame, somehow?
>
> Hm... I think I'm running only one frame. I'm running with emacs -nw.
> Does that support more than one frame, somehow? But, yes, my Gnus
> startup function has a call to
>
> (make-frame '((name . "emacs") (left . 0) (top . 0) (user-position . t)))
>
> in there. I always start up two frames under X, but I didn't think that
> that call did anything under emacs -nw.
What does frame-list return after you start emacs -nw like that?
> Let's see. I'll try to start Emacs (with -nw) without that call.
>
> Aha! Now there's no fluttering and no extra refreshes going on! That
> might explain why I've never been able to reproduce this bug with a
> simple test case.
>
> > The marked call to SET_FRAME_VISIBLE would set the frame's garbaged
> > flag. The solution was to avoid doing that if FRAME is already the
> > top frame shown on that terminal (the EQ test and the comment before
> > it were added as part of fixing that bug). Perhaps in your case this
> > logic is somehow not working?
>
> Sounds likely.
>
> Here's a couple seconds' worth of output from the recipe:
>
> Hardware watchpoint 4: ((struct frame *) 0xc12be0)->garbaged
>
> Old value = 1
> New value = 0
> clear_garbaged_frames () at xdisp.c:10729
> 10729 f->resized_p = 0;
> Hardware watchpoint 4: ((struct frame *) 0xc12be0)->garbaged
>
> Old value = 0
> New value = 1
> 0x0000000000420725 in do_switch_frame (frame=12659685, track=1, for_deletion=0, norecord=12571250) at frame.c:844
> 844 SET_FRAME_VISIBLE (XFRAME (frame), 1);
We are close. What I need to know now is what is 'frame" and what is
'top_frame' at this point. You can define this as the watchpoint's
commands:
> pp frame
> pp top_frame
> continue
> end
Then run the recipe again, and let's see what this shows.
Thanks.
next prev parent reply other threads:[~2013-08-05 18:45 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
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 [this message]
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=83fvuovuvx.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 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.