unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Eli Zaretskii <eliz@gnu.org>, 71049@debbugs.gnu.org
Subject: bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process"
Date: Sat, 25 May 2024 19:00:19 +0200	[thread overview]
Message-ID: <87jzjhvnbw.fsf@gmx.de> (raw)
In-Reply-To: <608acf89-a1f9-4151-9f53-99962af87688@gutov.dev> (Dmitry Gutov's message of "Sat, 25 May 2024 19:17:03 +0300")

Dmitry Gutov <dmitry@gutov.dev> writes:

> Hi Michael,

Hi Dmitry,

> Either of my patches would let the user avoid having to choose between
> functionality and performance. Though I suppose some (many?) would
> prefer to disable the remote history ring altogether, for extra
> performance.

I'll have another idea.

shell-mode checks already, whether the histfile is equal
null-device. That works for the local case only.

However, in Tramp there is tramp-histfile-override. It let's you decide
whether you want to use the remote histfile, or use a histfile given by
a file name, or don't use a histfile.

This works for normal sync and async processes, but not for direct async
processes (IIRC). Let's see whether I could extend this mechanism, and
provide shell-mode proper information.

If a user sets tramp-histfile-override to t or "/dev/null", shell-mode
should not read the remote histfile. Users are already conditioned to
set this user option :-)

WDYT? I'll work on this tomorrow.

Best regards, Michael.





  reply	other threads:[~2024-05-25 17:00 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-19  0:19 bug#71049: async-shell-command ends with "Process *Async Shell Command* finished" when remote "direct-async-process" Dmitry Gutov
2024-05-19  6:17 ` Eli Zaretskii
2024-05-19 12:40   ` Dmitry Gutov
2024-05-24 11:15 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-24 14:06   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-24 14:50     ` Eli Zaretskii
2024-05-24 16:39       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-24 18:55         ` Eli Zaretskii
2024-05-24 19:20           ` Dmitry Gutov
2024-05-25 10:49             ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-25 13:54               ` Dmitry Gutov
2024-05-25 15:51                 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-25 16:17                   ` Dmitry Gutov
2024-05-25 17:00                     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-05-25 17:31                       ` Dmitry Gutov
2024-05-25 17:44                         ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-26 14:18                           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29  1:59                             ` Dmitry Gutov
2024-05-29  7:41                               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 11:55                                 ` Dmitry Gutov
2024-05-29 15:19                                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 11:53                               ` Eli Zaretskii
2024-05-29 11:57                                 ` Dmitry Gutov
2024-05-29 12:46                                   ` Eli Zaretskii
2024-05-29 17:26                                     ` Dmitry Gutov
2024-05-29 17:42                                       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 18:15                                         ` Dmitry Gutov
2024-05-29 18:38                                           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 20:40                                             ` Dmitry Gutov
2024-05-30  8:49                                               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-31  0:24                                                 ` Dmitry Gutov
2024-05-31  5:53                                                   ` Eli Zaretskii
2024-05-31 16:24                                                     ` Dmitry Gutov
2024-05-31 18:05                                                       ` Eli Zaretskii
2024-06-01  1:21                                                         ` Dmitry Gutov
2024-06-01  6:07                                                           ` Eli Zaretskii
2024-06-01 15:33                                                             ` Dmitry Gutov
2024-06-01 15:47                                                               ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-02  1:39                                                                 ` Dmitry Gutov
2024-06-02  8:36                                                                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-02 14:10                                                                     ` Dmitry Gutov
2024-06-02 14:46                                                                       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-02 15:01                                                                         ` Dmitry Gutov
2024-06-02 17:31                                                                           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-31  7:27                                                   ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-31 12:13                                                     ` Dmitry Gutov
2024-05-29 18:11                                       ` Eli Zaretskii
2024-05-25 17:10                   ` Eli Zaretskii
2024-05-25  7:23           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-24 17:17     ` Dmitry Gutov
2024-05-24 17:41       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-24 17:50         ` Dmitry Gutov
2024-05-24 18:09           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-25 13:03 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-25 14:40   ` Dmitry Gutov
2024-05-25 15:26     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87jzjhvnbw.fsf@gmx.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71049@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).