From: "Stuart D. Herring" <herring@lanl.gov>
Cc: emacs-devel@gnu.org
Subject: Re: [EPeterson@mcdonaldbradley.com: Kill ring leak in winemacs macros]
Date: Thu, 18 Aug 2005 10:52:02 -0700 (PDT) [thread overview]
Message-ID: <44802.128.165.123.83.1124387522.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <de2ek5$kkv$1@sea.gmane.org>
> I think you mean it should be checked while defining a macro, as well as
> when executing one, because the first time a macro is executed is when
> it is defined -- right?
The idea is that a macro running without user interaction -- one that may
take minutes to run (repeatedly) -- shouldn't interact with the window
system clipboard because the user may be doing so concurrently. I think
it's more than a bit strange to use the system clipboard (presumably using
windows other than Emacs) while defining a keyboard macro that itself uses
kill-ring commands, since the interaction with the window system (and/or
other applications) can't be included in the macro.
In other words, it doesn't make much sense to define a macro while you're
copying text between windows. It does make sense to run a macro while
you're copying text, and the two operations shouldn't interfere.
Moreover, while defining a macro the user is in control and the clipboard
is thus in control; while running a macro there's no such connection. So
I think that doing this separation during macro execution is sufficient.
> > One point, remains, though: Richard said he wanted the kill-ring
> > re-synchronized with the external world at the end of a keyboard macro
> > that desynched them; I guess that would have to go in
> execute-kbd-macro.
> > But what should happen if both Emacs and the window system have new
> text
> > at that point (where no ordering exists between them)?
>
> Where did he say that?
http://lists.gnu.org/archive/html/emacs-devel/2005-08/msg00108.html
Jason Rumney made a reasonable suggestion in
http://lists.gnu.org/archive/html/emacs-devel/2005-08/msg00778.html, but
I'd like to hear Richard's answer to the question (if he has a
preference), since he raised the issue.
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.
next prev parent reply other threads:[~2005-08-18 17:52 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
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 [this message]
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=44802.128.165.123.83.1124387522.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--cc=emacs-devel@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).