Achim Gratz <strom...@nexgo.de> writes: >> The use of "/bin/sh" as fallback should be OK. In the local case, the >> first cond clause shall be selected (otherwise there is something really >> wrong). > > Yes. But on Windows there is always something wrong… :-)
Again: under Windows, on the local host, `shell-file-name' should do. For the remote case you are right, but I doubt that any org user has ever tried to run a remote Windows shell via Tramp. >> And for remote execution, "/bin/sh" should exist execept in case >> of remote MS Windows or Android devices. Once you want run shells from >> org there, we could even tweak this :-) > > I was thinking towards being able to use a restricted shell. `shell-file-name' is your friend. "/bin/sh" is just the last resort. If you dislike it, you could raise an error instead :-) > Regards, > Achim. Best regards, Michael.
