unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stuart D. Herring" <herring@lanl.gov>
Cc: rms@gnu.org
Subject: Re: [EPeterson@mcdonaldbradley.com: Kill ring leak in winemacs  macros]
Date: Wed, 3 Aug 2005 12:27:01 -0700 (PDT)	[thread overview]
Message-ID: <34161.128.165.123.83.1123097221.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <E1E0Od0-0002Ey-1f@fencepost.gnu.org>

> I don't entirely understand this, but I suggest that someone who uses
> Windows read it and DTRT.

This doesn't seem to be Windows-specific at all; he says that using the
system clipboard while running a (long/repeated) macro that uses Emacs'
kill ring loses because they're constantly being synchronized.  That
should be true on any system with interprogram cut/paste.

He also attributes a perceived slowness on W32 to this synchronization,
but that seems unlikely (I'd think it more likely to be slower redisplay
or so on W32).

So, what he really wants is to not have the system clipboard consulted or
updated during the execution of a keyboard macro, when the kill-ring
should be "internal" data.  If that sounds like a good idea, I can whip up
a patch.

Davis Herring

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.

  reply	other threads:[~2005-08-03 19:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 19:10 [EPeterson@mcdonaldbradley.com: Kill ring leak in winemacs macros] Richard M. Stallman
2005-08-03 19:27 ` Stuart D. Herring [this message]
2005-08-03 19:52   ` Lennart Borgman
2005-08-03 20:59     ` Stuart D. Herring
2005-08-03 21:41       ` Lennart Borgman
2005-08-04  3:55         ` Eli Zaretskii
2005-08-04  7:25           ` Lennart Borgman
2005-08-03 23:12       ` Kevin Rodgers
2005-08-04 15:34         ` Stuart D. Herring
2005-08-16 15:07         ` Stuart D. Herring
2005-08-16 16:10           ` Jason Rumney
2005-08-16 16:19             ` Jason Rumney
2005-08-17  6:24               ` Richard M. Stallman
2005-08-18 16:43               ` Kevin Rodgers
2005-08-18 21:15                 ` Jason Rumney
2005-08-18 22:17                   ` Stuart D. Herring
2005-08-16 16:31             ` Stuart D. Herring
2005-08-16 21:38               ` Jason Rumney
2005-08-18 16:57                 ` Kevin Rodgers
2005-08-18 16:56               ` Kevin Rodgers
2005-08-18 17:52                 ` Stuart D. Herring
2005-08-04 12:48       ` Richard M. Stallman
     [not found]   ` <E1E0f9R-0003Pk-NJ@fencepost.gnu.org>
2005-08-04 14:19     ` Lennart Borgman
2005-08-04 15:20     ` Juanma Barranquero
2005-08-05 11:59       ` Richard M. Stallman
2005-08-05 12:43         ` Juanma Barranquero
2005-08-06  6:27           ` Richard M. Stallman
2005-08-05 13:48         ` defadvice in Emacs code (was: " Lennart Borgman

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=34161.128.165.123.83.1123097221.squirrel@webmail.lanl.gov \
    --to=herring@lanl.gov \
    --cc=rms@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).