Jeffrey Gennari <[email protected]> writes: > Hi Michael,
Hi Jeffrey, > Attached is the base64 encoded debug buffer. Thanks. The prompt from the remote shell is a single "$", no space. In theory, this shouldn't matter; Tramp shall recognize this prompt as well. Strange. What puzzles me a bit is, that Tramp sends commands not common for the initialization step. I have the impression, that you run all these tests from an Emacs, which has already a Tramp history. Maybe you could rerun the test from a fresh plain Emacs. Please try the following: --8<---------------cut here---------------start------------->8--- emacs -Q --eval '(setq tramp-verbose 10)' /ssh:jsg@pd2: --8<---------------cut here---------------end--------------->8--- If this also fails, maybe you could try it from another machine. Your local machine runs macOS, using a GNU/Linux machine could change the results. At least we would know that it isn't a problem of the remote machine. Another idea is to try latest Tramp sources from git. Recently, there has been a problem with macOS, which was fixed there. However, the situation was different to yours, it was a problem using Tramp on a local MS Windows machine, connecting a remote macOS machine. Unfortunately, I'm bad in testing macOS. I do not run such a machine, neither local nor remote. > Thanks, > Jeff Best regards, Michael. _______________________________________________ Tramp-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/tramp-devel
