Re: MPS: Win64 testers?

[Quang Kien Nguyen]

> Not clearly enough.  Consoles are tricky on Windows.  It is better to
> start Emacs with stderr redirected to a file (I've shown how to do
> that in a previous message), and then see that what the child Emacs
> writes to external-debugging-output does not appear in that file.
>
> Also, instead of start-process please use call-process.  That's
> because start-process redirects the stdout/stderr handles of the child
> process to the pipe from which the parent Emacs process reads, and
> that makes the experiment more complex and harder to reason about.
>
> And one more thing: when using "emacs --batch", it is easier to use
> 'message' to write to stderr; no need to 'print' via
> external-debugging-output.

Okay, I've tried with redirecting the stderr to file and then use
    (print 10 #'external-debugging-output)

10 is printed in the file.

Then try with
    (call-process "emacs" nil nil nil "--batch" "-Q" "--eval"
"(message \"20\")")

The child emacs process is created but nothing appended to the output file.
Is that okay?

I have the Emacs binary prebuilt here for UCRT [1], please give it a try if you
want to test more.


[1] https://github.com/kiennq/emacs-build/releases/tag/v31.279.20240807.fa1ecbf