bug#57676: 29.0.50; Tramp: Unable to close vterm buffer with remote default-directory

[Michael Albinus <michael.albinus@gmx.de>]

James Ferguson <james@faff.org> writes:

Hi James,

> I can confirm the latest build no longer causes me that problem.

Thanks for the feedback!

> It's not vterm's fault, it's mine.  I set `default-directory` like
> that when spawning it, which I have just been getting away with for a
> long time.  It seems up until now a lot of things have been tolerant
> of my invalid local path, with empty, '.' or './' seemingly being
> treated like '~' before now.
>
> So I'll be fixing my code that created a badly formed
> default-directory as well.

Good to know ther's no error in Tramp or vterm.

> Thank you for your efforts!  I'm very glad to see Tramp is getting
> some attention.  I love it and rely on it but it adds a lot of latency
> for me with its extensive round trips when establishing connections (I
> have to ssh via an AWS jumphost).

The Tramp FAQ has an item "How to speed up TRAMP?", see
(info "(tramp) Frequently Asked Questions")

Perhaps you could profit from the recommendations.

Best regards, Michael.