[sawfish] Command `xterm' bugfix. It didn't run if the optional argument as a command is not set.

[Christopher Bratusek <chrisb src gnome org>]

commit 7442ce348c7dbaa697566707543f45e1bdb49c24
Author: Teika kazura <teika lavabit com>
Date:   Sat Aug 21 08:04:49 2010 +0900

    Command `xterm' bugfix.
    It didn't run if the optional argument as a command is not set.

 lisp/sawfish/wm/commands/launcher.jl |    3 ++-
 man/news.texi                        |    4 ++++
 2 files changed, 6 insertions(+), 1 deletions(-)
---
diff --git a/lisp/sawfish/wm/commands/launcher.jl b/lisp/sawfish/wm/commands/launcher.jl
index 70408fb..86e533f 100644
--- a/lisp/sawfish/wm/commands/launcher.jl
+++ b/lisp/sawfish/wm/commands/launcher.jl
@@ -51,7 +51,8 @@
     "Start a new terminal. Optional argument `COMMAND' is passed to the
 terminal with -e option, so for most, including xterm, it can contain
 arguments to be passed."
-    (if (not command)
+    (if (or (not command)
+	    (equal "" command))
 	(system (format nil "%s >/dev/null 2>&1 </dev/null &"
 			xterm-program))
       ;; Note that -e has to be the last argument. See man xterm.
diff --git a/man/news.texi b/man/news.texi
index c38d4f5..9ac1d30 100644
--- a/man/news.texi
+++ b/man/news.texi
@@ -110,6 +110,10 @@ always black (therefore possibly invisible), on the other hand those
 numbers weren't erased from the screen (unless you used a
 desktop-shell which on it's own refreshes the screen regularly). Both
 issues have been fixed by introducing the @code{x-draw-text} function.
+
+ item Command @code{xterm} fix [Teika kazura] *
+It didn't run if the optional ``command'' argument was unset by the
+configurator, i.e. if it was an empty string.
 @end itemize
 
 @item New Features