Re: [O] [BUG] remote execution in heterogeneous environment

[Achim Gratz]

Michael Albinus writes:
> +  (let ((input-file (org-babel-temp-file "input-"))
> +     (error-file (if error-buffer (org-babel-temp-file "scor-") nil))
> +     (shell-file-name
> +      (if (file-executable-p
> +           (concat (file-remote-p default-directory) shell-file-name))
> +          shell-file-name
> +        "/bin/sh"))

The hard-coded /bin/sh breaks testing with NT-Emacs and using Cygwin as
the backend because of the different path conventions in both
environments.  This is a hack, but it works when setting SHELL=dash,
note that there are no path components in there and even if your test
would fail: NTEmacs knows nothing about Cygwin's path.  Can you please
arrange that shell-file-name is used without alteration when the
execution is local?  Even for remote execution hardcoding /bin/sh seems
a bit heavy-handed to me…


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada