Daniel Colascione <dancol@dancol.org> writes:

Hi Daniel,

> When the remote shell emits bracketed paste escape codes (as zsh does
> even when TERM=dumb), tramp ends up timing out unable to find the shell
> prompt on initial connection.

Have you checked the recipe from the Tramp manual in (info "(tramp)
Frequently Asked Questions") ?

--8<---------------cut here---------------start------------->8---
          When using zsh on remote hosts, disable zsh line editor
          because zsh uses left-hand side and right-hand side prompts in
          parallel.  Add the following line to ‘~/.zshrc’:

               [[ $TERM == "dumb" ]] && unsetopt zle && PS1='$ ' && return

          This uses the default value of ‘tramp-terminal-type’, "dumb",
          as value of the ‘TERM’ environment variable.  If you want to
          use another value for ‘TERM’, change ‘tramp-terminal-type’ and
          this line accordingly.
--8<---------------cut here---------------end--------------->8---

Note, that until recently TERM wasn't set properly initially, when
calling ssh. I have a WIP patch for this (being under regression test
for some days), see appended. Does this help?

> BTW: is there any particular reason that sshx uses RemoteCommand but ssh
> method does not?

Yes: They are different methods, and they are designed for this
difference. For example, using RemoteCommand disables direct async
processes for sshx connections.

Best regards, Michael.