*** no comment ***

2 files changed, 11 insertions, 2 deletions

diff --git a/TODO b/TODO
index 5c70ad9..7af2686 100644
--- a/TODO
+++ b/TODO
@@ -1,3 +1,11 @@
+Don't ever use chess-pos-move directly, but instead create ply and
+call chess-ply-next-pos.  This will make sure that castling moves are
+interpreted correctly.
+
+Pawn captures while playing gnuchess cause an error.
+
+Is the whole event model just a bit too fragile?
+----------------------------------------------------------------------
 * 2.0
 
 ** Breakdown
diff --git a/chess-display.el b/chess-display.el
index 526d8ca..5f11e56 100644
--- a/chess-display.el
+++ b/chess-display.el
@@ -86,7 +86,7 @@
 	 (draw (intern-soft (concat name "-draw")))
 	 (highlight (intern-soft (concat name "-highlight")))
 	 (initialize (intern-soft (concat name "-initialize"))))
-    (unless initialize
+    (unless draw
       (error "There is no known chessboard display style '%s'" name))
     (with-current-buffer (generate-new-buffer "*Chessboard*")
       (setq cursor-type nil
@@ -96,7 +96,8 @@
 	    chess-display-perspective perspective
 	    chess-display-search-function search-func)
       (chess-display-mode)
-      (funcall initialize)
+      (if initialize
+	  (funcall initialize))
       (if session
 	  (let ((game (chess-session-data session 'current-game)))
 	    (if game