Re: Remote process attributes

[Eli Zaretskii <eliz@gnu.org>]

> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: emacs-devel@gnu.org
> Date: Mon, 04 Apr 2022 13:33:59 +0200
> 
> > Is it really certain that the default-directory being remote is
> > evidence significant enough that the user wants to list remote
> > processes?  Processes aren't files, and aren't even related to files
> > like programs (whose executable files are looked up before we run
> > them).
> 
> I've checked all occurences of list-system-processes and
> process-attributes in core Emacs, GNU ELPA and NonGNU ELPA. This is just
> a handful, and all of them could preserve their behavior with the
> template I've shown. Really not a big deal.
> 
> If both functions are used somewhere else in the future, the
> documentation tells what to do. And I could imagine that this
> information about remote processes could be used not only in proced.

Using Proced is what I had in mind.  AFAIU, if Proced is invoked with
default-directory being on a remote host, it will show remote
processes after your changes.  I'm asking whether users will indeed
expect that.

> What we could think about is a way to indicate proced whether to return
> local or possibly remote process information. I wanted to add a prefix
> argument to proced in order to trigger remote process information, but
> this is already used for window selection.

We could use a special value of the argument to work around this.