From: Perry Smith <pedzsan@gmail.com>
To: Emacs Help <help-gnu-emacs@gnu.org>
Subject: Paste takes 10 seconds
Date: Wed, 2 Oct 2013 12:43:44 -0500 [thread overview]
Message-ID: <250C3573-2F70-472C-8655-4E7F57B25E5B@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
My arrangement is a VNC client (JollyVNC) on a Mac connected to a RealVNC server on an AIX host. The AIX host is running emacs as an X11 client using the VNC's window. The emacs is 24.3.
If I do "kill" and "yank" within emacs, its fine. But if I copy from another window (e.g. a native window on the Mac) and then move to the emacs window and do a yank, it takes about 10 seconds for it to produce the text.
This started in 24.2 I 99% sure. When I moved to emacs 24, I had to get a new VNC server because emacs broke (removed) the cut buffer support under the belief that no one used it -- but I guess I was still using it.
Has anyone else seen this? Any suggestions of what emacs might be doing for 10 seconds? Or how to track this down?
Thank you,
Perry
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
reply other threads:[~2013-10-02 17:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=250C3573-2F70-472C-8655-4E7F57B25E5B@gmail.com \
--to=pedzsan@gmail.com \
--cc=help-gnu-emacs@gnu.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.
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).