all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Welsh Duggan <md5i@md5i.com>
Cc: 10195@debbugs.gnu.org, ejb@ql.org
Subject: bug#10195: 24.0.92; M-w may no longer provide visual feedback
Date: Sat, 03 Dec 2011 18:38:03 +0200	[thread overview]
Message-ID: <83r50lbogk.fsf@gnu.org> (raw)
In-Reply-To: <878vmty979.fsf@maru.md5i.com>

> From: Michael Welsh Duggan <md5i@md5i.com>
> Cc: ejb@ql.org,  10195@debbugs.gnu.org
> Date: Sat, 03 Dec 2011 10:19:06 -0500
> 
> I just tried this again in a random buffer in my running non -Q emacs.
> The first M-w caused the cursor to bounce, the second did not, the third
> did, the fourth and fifth did not.  This is why I called the behavior
> inconsistent.  I just tried it in emacs -Q again, and had it bounce
> three times out of 15 tries.

Does "C-h l" show all the 15 M-w keystrokes you did?

> I am running in an unoptimized debug build with assertions turned on,
> and am familiar with gdb.  If there is any way I can help debug this,
> please let me know.

M-w calls sit-for after bouncing point to the position of mark; the
default waiting period is 1 sec.  How about instrumenting sit-for with
calls to `message' and seeing what's going on there?  One possibility
is that some input event terminates the wait immediately (see
sit-for's code).  Another possibility is that something happens in
read-event, in which case you will need to use GDB.  But I think it
would be good to see what's going on in sit-for before you go to the C
level.

Another idea is to replace the call to sit-for in kill-ring-save with
a call to sleep-for, and see if that changes anything.  If it does,
the probably culprit is sit-for and whatever it calls.

Thanks.





  parent reply	other threads:[~2011-12-03 16:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 16:09 bug#10195: 24.0.92; M-w may no longer provide visual feedback Jay Berkenbilt
2011-12-02 16:23 ` Eli Zaretskii
2011-12-03  5:31   ` Michael Welsh Duggan
2011-12-03  7:09     ` Eli Zaretskii
2011-12-03 15:19       ` Michael Welsh Duggan
2011-12-03 15:22         ` Michael Welsh Duggan
2011-12-03 16:38         ` Eli Zaretskii [this message]
2011-12-03 17:05           ` Eli Zaretskii
2011-12-03 17:38           ` Michael Welsh Duggan
2011-12-04  2:29           ` Chong Yidong
2011-12-04  3:29             ` Michael Welsh Duggan
2011-12-04  3:59             ` Eli Zaretskii
2011-12-04  8:11               ` Chong Yidong
2011-12-04 11:25                 ` Eli Zaretskii
2011-12-04 15:59                   ` Chong Yidong
2011-12-04 16:58                     ` Eli Zaretskii
2011-12-05  3:29                       ` Stefan Monnier
2011-12-05 15:17                       ` Chong Yidong

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=83r50lbogk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=10195@debbugs.gnu.org \
    --cc=ejb@ql.org \
    --cc=md5i@md5i.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 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.