Re: Buffer mode in start-process-shell-command vs async-shell-command

> I mean, just like async-shell-command, start-process-shell-command
> should also use Shell mode, since both of them are running shell
> command. Why doesn't it? Is that a bug?

`start-process-shell-command` is a lower-level function that just starts
a process via a shell command.  It is not expected in general that the
users will directly interact with that process: instead some ELisp code
will be in charge of sending data and processing he output.  In many
cases, the buffer will not even be displayed to the user.

In contrast `async-shell-command` is a user-level command, where the
buffer is expected to be displayed and the user is expected to be able
to interact with the process (e.g. to send further input).

IIRC, for those same reasons, those two functions may not necessarily
use the same shell: `start-process-shell-command` will use the system's
shell, while `async-shell-command` might use the user's favorite shell.


=== Stefan