Hi Pete, >>>>> [email protected] writes: >> Do you mean that only a single "#" appeared in the echo area? Not >> "#"? And didn't emacs signal an error?
> Oops, pardon me, rest of the line in my posting got swallowed up; "#" > is what I get, you are correct. Ah, I see. Your MUA seems broken at generating plain text alternative part. I guess it dismisses everything between "<" and ">", whereas it retains "<something>" in the html alternative. Probably "FreeMail powered by mail.de" is responsible for that. (I prefer plain text over html format, so I configured my MUA to display plain text alternative rather than html alternative.) Then emacs thinks that asynchronous TeX process has started successfully. The problems is that the process actually doesn't run. >> Hmm... What happens when you issue the following command on the wsl bash >> console? (not in emacs) >> bash -c "tex.exe --version" & > This: [1] 21 TeX 3.141592653 (TeX Live 2022) [...] OK. Then windows binary runs without problem when it is called indirectly through "bash -c" under asynchronous invocation. I think that you have cmd.exe in your PATH and expect that cmd.exe on wsl console opens windows command prompt. If it does, close it by entering "exit" at the prompt and try the following: 1. Start wsl emacs session and load AUCTeX (i.e., open some (La)TeX document.) 2. Insert (start-process "dummy" (current-buffer) TeX-shell TeX-shell-command-option "cmd.exe") at the last of *scratch* buffer and type C-x C-e just after the closing ")". Does it open a windows command prompt successfully? If not, what does emacs report? Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine
