GNU bug report logs -
#71049
async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process"
Previous Next
Reported by: Dmitry Gutov <dmitry <at> gutov.dev>
Date: Sun, 19 May 2024 00:20:02 UTC
Severity: normal
Done: Dmitry Gutov <dmitry <at> gutov.dev>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Hi Michael,
On 30/05/2024 11:49, Michael Albinus wrote:
>> Thank you. I haven't tested this personally either, but it seems like
>> this is the behavior we will want by default.
>>
>> So the proposed solution should include it, I think.
> In order to not misunderstand: you agree the solution based on
> tramp-histfile-override now, don't you?
Just to be frank: I don't like the approach, but I do think it's better
than the status quo. In that sense, I agree with it, if none other is
accepted.
But, well, in the meantime I came up with a couple of new solutions:
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.
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.
2) [second patch] async-shell-command could set shell--start-prog (it's
permanent-local) to `none', and then shell-mode will check for that
value, and if set to this value, skip the input ring setup.
Downsides? Pretty ad-hoc approach. And any external code looking up this
(private) variable could be surprised by the new value.
[shell-command-mode.diff (text/x-patch, attachment)]
[shell-start-prog-none.diff (text/x-patch, attachment)]
This bug report was last modified 1 year and 81 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.