Fix a recently-added Eshell test on MS-Windows

* test/lisp/eshell/esh-var-tests.el
(esh-var-test/last-result-var-ext-cmd): Fix the test on
MS-Windows by making sure the internal 'format' command
is invoked.  (Bug#57129)
This commit is contained in:
Eli Zaretskii 2022-08-13 09:58:44 +03:00
parent f3408af0a3
commit 6de88b6b02

View file

@ -561,10 +561,13 @@ This tests when `eshell-lisp-form-nil-is-failure' is nil."
"Test using the \"last result\" ($$) variable with an external command"
(skip-unless (executable-find "["))
(with-temp-eshell
(eshell-command-result-p "[ foo = foo ]; format \"%s\" $$"
"t\n")
(eshell-command-result-p "[ foo = bar ]; format \"%s\" $$"
"nil\n")))
;; MS-DOS/MS-Windows have an external command 'format', which we
;; don't want here.
(let ((eshell-prefer-lisp-functions t))
(eshell-command-result-p "[ foo = foo ]; format \"%s\" $$"
"t\n")
(eshell-command-result-p "[ foo = bar ]; format \"%s\" $$"
"nil\n"))))
(ert-deftest esh-var-test/last-result-var-split-indices ()
"Test using the \"last result\" ($$) variable with split indices"