Kevin Rodgers wrote: > > Then `kill-new', `kill-append', and `current-kill' would be modified to > > ignore `interprogram-*-function' if `macro-private-kills' is set and a > > keyboard macro is executing. > > It would be simpler to temporarily bind the interprogram-*-functions > variables to nil in execute-kbd-macro.
I realize I never did implement this -- can I get some opinions on which of these approaches to follow? So far my reasoning is that the execute-kbd-macro path is simpler and cleaner, but the kill-functions path is more transparent (as well as having the trivial advantage that it would remain possible to permanently affect the interprogram-*-functions variables from a keyboard macro). 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. _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel
