- 23 Nov, 2016 2 commits
-
-
Francois-Rene Rideau authored
Always go through CMD in that case, including on Allegro and CLISP, since the previous behavior is simultaneously non-portable, error-prone and limited; better to provide a portable well-defined abstraction. Users who want more can use the (bad) implementation-specific interfaces, or IOlib. Simplify the call to RUN-PROGRAM. Add a PARAMETER-ERROR to %NORMALIZE-COMMAND on unsupported platforms.
-
Elias Pipping authored
We cannot use `exit` on Windows with :force-shell nil (it's a builtin); use `cmd /c exit` instead. Using `exit` on Unix with :force-shell nil may or may not work (it's a builtin but CL implementations typically invoke a shell anyway). `true` and `false` are guaranteed to exist by the POSIX standard.
-
- 22 Nov, 2016 13 commits
-
-
Francois-Rene Rideau authored
-
Elias Pipping authored
-
Robert Goldman authored
Use of PATHNAME-MATCH caused spurious test failures on clisp.
-
Robert Goldman authored
-
Elias Pipping authored
With ECL it causes problems. On other platforms it should not be necessary. This gets run-program with ECL on windows far closer to working again
-
Elias Pipping authored
-
Francois-Rene Rideau authored
This requires a patch to sb-impl::prepare-args relative to sbcl 1.3.10.
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Francois-Rene Rideau authored
-
Elias Pipping authored
-
Elias Pipping authored
cmd has an echo command. but there is no binary by that name without cygwin
-
- 20 Nov, 2016 3 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
Fix ecl require test Choosing `serve-event` as the test module for testing require on ECL seems not to work. AFAICT, `rt` is a good choice because not loaded by default and it seems to be installed by default on linux, mac, and windows. See merge request !53
-
Robert Goldman authored
-
- 19 Nov, 2016 1 commit
-
-
Robert Goldman authored
-
- 15 Nov, 2016 21 commits
-
-
Robert Goldman authored
-
Robert Goldman authored
Bug fix: Avoid ext:system on ECL ext:system is a wrapper around ext:run-program that forces :output nil, which is not something we want. See also https://bugs.launchpad.net/asdf/+bug/1638870 See merge request !48
-
Elias Pipping authored
-
Elias Pipping authored
-
Elias Pipping authored
The command returned by %redirected-system-command changes the current directory on its own.
-
Elias Pipping authored
-
Elias Pipping authored
ext:run-shell-command is deprecated but sys:run-program was not fully functional prior to version 1.4.0
-
Elias Pipping authored
-
Elias Pipping authored
ext:system is a wrapper around ext:run-program that forces :output nil, which is not something we want. See also https://bugs.launchpad.net/asdf/+bug/1638870
-
Elias Pipping authored
-
Elias Pipping authored
The check (lexicographic<= '< ver '(16 0 0)) Is equivalent to <=16.0.0. The argument '< gives the direction, and should not be '<= here.
-
Elias Pipping authored
launch-program no longer accepts a parameter :wait; since the call is surrounded by (wait-process ...), it would be superfluous anyway.
-
Elias Pipping authored
-
Robert Goldman authored
Bug/normalize io specifier fixes This makes tests pass again on Allegro CL and LispWorks after !49. See merge request !50
-
Elias Pipping authored
-
Elias Pipping authored
-
Robert Goldman authored
Have (run|launch)-program's :*put default to NIL Prior to this change, run-program's (but not launch-program's) :error-output and :input would default to :interactive if :output was interactive. See also https://bugs.launchpad.net/asdf/+bug/1638870 See merge request !47
-
Elias Pipping authored
Prior to this change, run-program's (but not launch-program's) :error-output and :input would default to :interactive if :output was interactive. See also https://bugs.launchpad.net/asdf/+bug/1638870
-
Robert Goldman authored
Mistakenly removed the else branch from (EQL :OUTPUT) case in %NORMALIZE-IO-SPECIFIER.
-
Robert Goldman authored
Complete branches in %NORMALIZE-IO-SPECIFIER. Per comments in !46 I think there is a danger that `%NORMALIZE-IO-SPECIFIER` could inappropriately return `NIL` when there is an unexpected set of `*FEATURES*`. I'll try to have a look and see if there are other cases like this. Elias, will you have a peek at what I've done here? See merge request !49
-
Robert Goldman authored
-