From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: despen@telcordia.com, 7092@debbugs.gnu.org
Subject: bug#7092: 23.1; Dired slow using Emacs remotely
Date: Sat, 18 Jan 2020 10:14:31 +0200 [thread overview]
Message-ID: <83sgkd18rc.fsf@gnu.org> (raw)
In-Reply-To: <87pnfhzipt.fsf@marxist.se> (message from Stefan Kangas on Sat, 18 Jan 2020 01:55:26 +0100)
> From: Stefan Kangas <stefan@marxist.se>
> Cc: Dan Espen <despen@telcordia.com>, 7092@debbugs.gnu.org
> Date: Sat, 18 Jan 2020 01:55:26 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Date: Thu, 23 Sep 2010 22:28:34 -0400
> >> From: Dan Espen <despen@telcordia.com>
> >> Cc:
> >>
> >> Moving the pointer around a dired buffer makes Emacs unusable for long
> >> periods of time. This is true even after disabling tool-tip
> >> mode.
> >
> > Probably because of the mouse highlight (which causes lots of X
> > traffic).
>
> I think the diagnosis here sounds correct. So is there anything here
> we can do? In other words, is this a bug in Emacs or just an inherent
> limitation in the X protocol?
Maybe we should have a feature whereby mouse highlight is ignored, for
those who use a slow X connection.
But is it indeed the case that X traffic caused by mouse highlight is
the culprit here?
next prev parent reply other threads:[~2020-01-18 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 2:28 bug#7092: 23.1; Dired slow using Emacs remotely Dan Espen
2010-09-24 8:05 ` Eli Zaretskii
2020-01-18 0:55 ` Stefan Kangas
2020-01-18 8:14 ` Eli Zaretskii [this message]
2020-01-18 8:23 ` Stefan Kangas
2021-10-21 19:43 ` Stefan Kangas
2021-10-22 5:55 ` Eli Zaretskii
2021-10-22 8:12 ` Stefan Kangas
2021-10-22 10:49 ` Eli Zaretskii
2021-10-24 22:08 ` Stefan Kangas
2021-10-25 11:49 ` Eli Zaretskii
2021-11-05 6:55 ` Stefan Kangas
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=83sgkd18rc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7092@debbugs.gnu.org \
--cc=despen@telcordia.com \
--cc=stefan@marxist.se \
/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.