Custom Query (1030 matches)

On linux:

 (with-output-to-string (out)
        (ccl:run-program
         "/bin/sh"
         '("-c" "echo hello")
         :input nil :output out :wait t))
"hello
"

which is the expected result.

On MS-Windows:

(with-output-to-string (out)
            (ccl:run-program
             "C:/cygwin/bin/sh"
             '("-c" "echo  hello")
             :input nil :output out :wait t))
"
"

which is not expected. Notice that run-program runs successfully:

(ccl:run-program
           "C:/cygwin/bin/sh"
           '("-c" "echo  hello")
           :input nil :output (make-string-output-stream) :wait t)
#<external-process (C:/cygwin/bin/sh -c
                    echo  hello)[nil] (exited : 0) #x2108DC3B8D>

but the output is not collected.

(list (lisp-implementation-type) (lisp-implementation-version)
               (machine-type) (machine-version))
("Clozure Common Lisp" "Version 1.7-r14925M  (Windowsx8664)" "x64" nil)

1.8-prerelease-r15247M (DarwinX8664)

In teh Search Files dialog, mis-queueing an In Folder choice, then searching, can require aborting a big silly search. Perhaps the search button could be converted into an Abort button. Meanwhile closing the dialog/search window causes this output in the AltConsole, Re-starting the Search Files dialog, changing the In Folder and leaves the Search button inoperable until the Find field is changed.

Error: #<STRING-OUTPUT-STREAM :CLOSED #x302000F57E2D> is closed While executing: CCL::STREAM-IS-CLOSED, in process Monitor thread for external process (grep -i -r -I -s -c -e defclass --include *.lisp /Users/user/)(15).

;;; ;;; #<PROCESS Monitor thread for external process (grep -i -r -I -s -c -e defclass --include *.lisp /Users/user/)(15) [Active] #x302000F573CD> requires access to Shared Terminal Input ;;; Type (:y 15) to yield control to this thread. ;;;

Dan Weinreb 2008-11-24 13:41:13 EST Section 11.1.2.1.2 of the CL manual says that it's "undefined" what happens if you try to rebind a symbol in the CL package. SBCL complains if you try to do a macrolet on a CL symbol, such as "log" (which actually happened). I think it would be nice if this caused a compiler warning or error. (As you may know, I am hoping to eliminate the places where our CCL buildbot succeeds but the SBCL buildbot fails. Often SBCL explicitly outlaws things that are defined to be undefined by the satndard.)