🚀 go-pugleaf

In the (unofficial) elisp manual, it says that if a process is communicating
by pipes instead of ptys (as determined by the global var
PROCESS-CONNECTION-TYPE) then the signalling functions (e.g.,
interrupt-process, kill-process, stop-process, and so forth) ignore their
second argument (CURRENT-GROUP).

Not so. If CURRENT-GROUP is T, these signals don't arrive. This is aggravated
by the fact that there's no advertised way to determine, given a process,
whether it's communicating via pipes or a pty.

For an example of this behavior, set PROCESS-CONNECTION-TYPE to nil,
crank up /bin/cat as a subprocess, and try (stop-process proc t)
and (stop-process proc nil).

Perhaps the manual is in error -- I don't know. If the manual is correct,
though, then this appears to be a bug in the signalling functions.

I might also add that it seems like a good idea to have a way to query a
process to find out its connection type.
	-Olin