> Is anyone else having trouble with tramp not properly setting the remote
> shell prompt?
I've never seen this problem. Hm.
> I just upgraded to 2.83. I've attached a patch that reorders the
> setting of the shell prompts that seems to help, though I can't say
> for sure. The rationale is that if you set PS2 and PS3 to '' before
> setting PS1 to a multiline prompt, you'll avoid the default PS2
> prompt of '>' from polluting your tramp buffer and possibly
> confusing tramp.
Now I'm confused. After sending the prompt-changing command, Tramp
waits for a newline, followed by tramp-end-of-output, followed by
another newline. So the problem could only happen when
tramp-end-of-output is ">", right?
I also just tested typing "PS2=''; PS3=''; PS1='" into a shell and
then hit the Return key, and I saw "> " on the next line. Hm. This
appears reasonable, since the shell reads a complete line before
executing the statements therein.
I'll be waiting for comments from others.
Simplification good! Oversimplification bad! (Larry Wall)