Daniel Gomez <d.go...@posteo.org> writes: > Hi Michael,
Hi Daniel, > thanks for the reply. Setting tramp-verbose to 10 helped me identify > the issue, and it was clearly related to the prompt. > I got it to work without issues after I changed the argument to --pty > from /usr/bin/zsh to /bin/sh. > I then noticed I had to play the rc trick on my zshrc to get it to > work with zsh: > > ``` > if [[ $TERM == "dumb" ]]; then > unsetopt zle && PS1='> ' > return > fi > ``` > > And now things work as expected. Thanks for the feedback. Good to know, that there's no error. I've modified the Tramp manual, clarifying the use of RemoteCommand. It reads now --8<---------------cut here---------------start------------->8--- *Note*: If you use an ‘ssh’-based method for connection, do _not_ set the ‘RemoteCommand’ option in your ‘ssh’ configuration to something like ‘screen’. If used, ‘RemoteCommand’ must open an interactive shell on the remote host. On the other hand, some ‘ssh’-based methods, like ‘sshx’ or ‘scpx’, silently overwrite a ‘RemoteCommand’ option of the configuration file. --8<---------------cut here---------------end--------------->8--- > I still have issues getting python to run, but I assume that is not > directly related to TRAMP, but rather to my configuration. > I'll continue investigating and hopefully that too will work soon. Let us know whether we could help you. > Kind regards, > Daniel Best regards, Michael.
