bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process"

[Dmitry Gutov]

On 31/05/2024 08:53, Eli Zaretskii wrote:

> > 1) [first patch] We can add a new major mode, for 'M-&' to use instead
> > of the full-blown 'shell-mode' - it could be very simple: just apply
> > font-lock keywords and maybe set list-buffers-directory.
>
> I think I'm okay with this.  (It needs to be prominently documented,
> of course.)

In NEWS?

> But we need a documented way for people to get previous
> behavior if they want that.  How would that work?

If we really needed the capability to rollback the change, I suppose we 
could add a defvar pointing to the major mode to use. I.e.

  (defvar async-shell-command-major-mode #'shell-command-mode)

> > Problems? I suppose someone might be using shell-mode-hook to do
> > something in the async-shell-command output buffer, and it won't fire
> > anymore. Seemingly very minor concern.
>
> Can't we run shell-mode-hook inside this new mode's mode hook?  Then
> this problem goes away.

Doesn't seem worth it - it was just an offhand example I came up with. 
The syntax table and the keymap would also different, and some user, in 
theory, could depend on those as well.