[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#71049: async-shell-command ends with "Process *Async Shell Command*
From: |
Eli Zaretskii |
Subject: |
bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process" |
Date: |
Fri, 24 May 2024 17:50:35 +0300 |
> Cc: 71049@debbugs.gnu.org
> Date: Fri, 24 May 2024 16:06:13 +0200
> From: Michael Albinus via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> >> 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’...done
> >
> > According 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.
>
> Eli?
Can you explain the effect of that option on the scenarios that
started this bug report? I don't think I have a clear understanding
of that.
Why is the process being called by such bogus names anyway?
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Dmitry Gutov, 2024/05/18
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Eli Zaretskii, 2024/05/19
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Michael Albinus, 2024/05/24
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Michael Albinus, 2024/05/24
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process",
Eli Zaretskii <=
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Michael Albinus, 2024/05/24
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Eli Zaretskii, 2024/05/24
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Dmitry Gutov, 2024/05/24
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Michael Albinus, 2024/05/25
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Dmitry Gutov, 2024/05/25
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Michael Albinus, 2024/05/25
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Dmitry Gutov, 2024/05/25
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Michael Albinus, 2024/05/25
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Dmitry Gutov, 2024/05/25
- bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process", Michael Albinus, 2024/05/25