|
From: | Dmitry Gutov |
Subject: | bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process" |
Date: | Fri, 24 May 2024 20:17:47 +0300 |
User-agent: | Mozilla Thunderbird |
Hi Michael, On 24/05/2024 17:06, Michael Albinus wrote:
The command can be simple, like 'ls' or 'echo 123'. I also see this added to*Messages*: Tramp: Inserting ‘/ssh:dgutov@fencepost.gnu.org:/home/d/dgutov/.tramp_history’...doneAccording to reading .tramp_history: this is performed in comint-read-input-ring, called from shell-mode. comint-input-ring-file-name is set in shell-mode, I don't see a trivial solution to suppress this. Likely, we must extend shell-mode for this case.We could add a user option remote-file-name-inhibit-input-ring which suppresses reading the remote histfile, when set to non-nil. See appended patch.
Maybe a good middle-ground solution would be to defer the reading of the history file until history is actually used?
E.g. in my examples there was no reading of input from the user, and there will be many read-life scenarios like that.
Perhaps commands like comint-previous-input could check whether the ring is not initialized yet and call comint-read-input-ring, rather than have this call performed eagerly at the end of shell-mode.
[Prev in Thread] | Current Thread | [Next in Thread] |