From: James Thomas via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Dima Kogan <dima@secretsauce.net>,
49954@debbugs.gnu.org, 60534@debbugs.gnu.org
Subject: bug#60534: 28.2; Forbidden reentrant call of Tramp
Date: Tue, 17 Dec 2024 18:41:53 +0530 [thread overview]
Message-ID: <86bjxafo86.fsf@gmx.net> (raw)
In-Reply-To: <87o71an24v.fsf@gmx.de> (Michael Albinus's message of "Tue, 17 Dec 2024 09:29:36 +0100")
Michael Albinus wrote:
> Not so simple.
> ...
> And it isn't clear to me how to keep two connections in sync, if (for
> example) the environment changes in one of the connections. Be it an
> environment variable, the current directory, the availability of a
> temp file, you name it.
And here was I thinking that Tramp was mostly remote-state-less beyond
the handshake...
> There is a serious overhead when opening a new connection, due to the
> handshaking actions.
OK; I misremembered for a moment that it was beyond any ControlPersist.
> But yes, nobody has tried it yet. My preference is to use threads, so
> that one command in a process filter could wait until another command
> in the main thread has finished, as example. But the crucial point is,
> that you must activate threads in the beginning of a connection. When
> you detect, that there is a forbidded reentrant call, it is too late
> to activate threads.
Ah, crucial; but not a blocker, I suppose.
Thank you for the effort in explaining, Michael.
Regards,
James
next prev parent reply other threads:[~2024-12-17 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 9:08 bug#49954: 28.0.50; TRAMP: cannot kill child processes: "Forbidden reentrant call of Tramp" Dima Kogan
2021-08-09 12:33 ` Michael Albinus
2021-08-10 4:26 ` Dima Kogan
2021-08-10 13:52 ` Michael Albinus
2021-09-11 8:32 ` Dima Kogan
2021-09-11 12:19 ` Michael Albinus
2021-09-15 0:39 ` Dima Kogan
2021-09-15 19:25 ` Dima Kogan
2021-09-16 15:45 ` Michael Albinus
2021-09-16 15:42 ` Michael Albinus
2021-09-16 17:17 ` Dima Kogan
2021-09-16 17:36 ` Michael Albinus
2021-09-18 20:18 ` Dima Kogan
2021-09-18 20:50 ` Michael Albinus
2024-12-16 22:35 ` bug#49954: bug#60534: 28.2; Forbidden reentrant call of Tramp James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-17 8:29 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-17 13:11 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-03 20:52 Georgi Danov
2023-02-17 9:42 ` Michael Albinus
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=86bjxafo86.fsf@gmx.net \
--to=bug-gnu-emacs@gnu.org \
--cc=49954@debbugs.gnu.org \
--cc=60534@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--cc=jimjoe@gmx.net \
--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).