# HG changeset patch
# User Michael Kifer <kifer@cs.stonybrook.edu>
# Date 824507458 0
# Node ID 542db2bd7e382904e49c91a2b964b4eccb0dadb3
# Parent  298ed6bf5d2db0d810a92188cb57ae8d3e1690d9
(vip-events-to-macro): discard events represented as lists in macro
definitions.

diff -r 298ed6bf5d2d -r 542db2bd7e38 lisp/emulation/viper-macs.el
--- a/lisp/emulation/viper-macs.el	Fri Feb 16 21:49:32 1996 +0000
+++ b/lisp/emulation/viper-macs.el	Fri Feb 16 21:50:58 1996 +0000
@@ -782,8 +782,21 @@
 	 (mapconcat 'char-to-string macro-name-or-body ""))
 	(t macro-name-or-body)))
     
+;; convert sequence of events (that came presumably from emacs kbd macro) into
+;; Viper's macro, which is a vector of the form
+;; [ desc desc ... ]
+;; Each desc is either a symbol of (meta symb), (shift symb), etc.
+;; Here we purge events that happen to be lists. In most cases, these events
+;; got into a macro definition unintentionally; say, when the user moves mouse
+;; during a macro definition, then something like (switch-frame ...) might get
+;; in. Another reason for purging lists-events is that we can't store them in
+;; textual form (say, in .emacs) and then read them back.
 (defun vip-events-to-macro (event-seq)
-  (vconcat (delq nil (mapcar 'vip-event-key event-seq))))
+  (vconcat (delq nil (mapcar (function (lambda (elt)
+					 (if (consp elt)
+					     nil
+					   (vip-event-key elt))))
+			     event-seq))))
   
 ;; convert strings or arrays of characters to Viper macro form
 (defun vip-char-array-to-macro (array)