public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stephen L <stephenl42@hotmail.com>
To: cygwin@cygwin.com
Subject: Re: Performance problems with emacs-X11 in current cygwin (attn: glib and gvim maintainer)
Date: Fri, 01 Jun 2012 16:23:00 -0000	[thread overview]
Message-ID: <loom.20120601T181510-676@post.gmane.org> (raw)
In-Reply-To: <4FC8A0E4.9000308@cornell.edu>

Ken Brown <kbrown <at> cornell.edu> writes:
> Fortunately for emacs users, the problem doesn't seem to occur with 
> emacs-24.  (Can anyone else confirm this?)

Hi Ken,

So I just upgraded to emacs-24 (24.0.96.1), and while it is certainly better, I
wouldn't say it's fixed.

Try opening a text file (I have a ~1000 line piece code).

If you mouse around in the X window, and left click, the emacs cursor is
sluggish to move.

In fact it appears the more mouse movement between clicks, the more sluggish
emacs is to respond.

Something not consuming PointerMotionMask events, perhaps?

best regards,
stephen

(edit to add: the gmane web interface has just given me "moron" as my captcha,
that is awesome!)


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2012-06-01 16:23 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 21:02 Performance problems with emacs-X11 in current cygwin Angelo Graziosi
2012-06-01 11:01 ` Performance problems with emacs-X11 in current cygwin (attn: glib and gvim maintainer) Ken Brown
2012-06-01 11:21   ` atelp
2012-06-01 11:57     ` Ken Brown
2012-06-01 16:23   ` Stephen L [this message]
2012-06-01 18:39   ` Ken Brown
2012-06-01 19:10     ` K Stahl
2012-06-02 14:15 ` Performance problems with emacs-X11 in current cygwin Angelo Graziosi
2012-06-02 15:09   ` Ken Brown
2012-06-02 19:03     ` Ken Brown
2012-06-03  9:08       ` Yaakov (Cygwin/X)
2012-06-03 12:11         ` Ken Brown
2012-06-03 17:01           ` Ken Brown
2012-06-06 11:05             ` Stephen L
2012-06-08 12:59               ` Ken Brown
2012-06-08 15:33                 ` Achim Gratz
2012-06-08 16:46                   ` Ken Brown
2012-06-08 19:35                     ` Andrey Repin
2012-06-11  0:45                     ` Ken Brown
2012-06-11  2:54                       ` Yaakov (Cygwin/X)
2012-06-11 11:39                         ` Ken Brown
2012-06-11 15:11                           ` Ken Brown
2012-06-12 13:02                             ` Ken Brown
2012-06-11 13:56                       ` K Stahl
2012-06-11 14:54                         ` Ken Brown
2012-06-11 16:15                           ` K Stahl
2012-06-11 17:59                             ` Ken Brown
2012-06-11 18:56                               ` K Stahl
2012-06-13 18:40                       ` Ken Brown
2012-06-13 21:07                         ` Ken Brown
2012-06-13 21:40                           ` Christopher Faylor
2012-06-14 19:19                             ` Ryan Johnson
2012-06-14 19:48                               ` Ken Brown
2012-06-13 23:58                           ` K Stahl

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=loom.20120601T181510-676@post.gmane.org \
    --to=stephenl42@hotmail.com \
    --cc=cygwin@cygwin.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.
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).