Re: tramp ($Id: tramp.el,v 1.440 2001/01/18 23:20:57 grossjoh Exp $); Yet another "Couldn't find exit status of `ls -d' command"

E Jason Riedy <[EMAIL PROTECTED]> writes: [...] > Mark me as another person stuck at the initial login. Every encrypted > mode I've tried hoses, but I haven't tried any non- encrypted mode. A > (sit-for 1) directly after the "echo hello" solves the problem. > Un-commenting the one before all th

tramp ($Id: tramp.el,v 1.440 2001/01/18 23:20:57 grossjoh Exp $); Yet another "Couldn't find exit status of `ls -d' command"

Enter your bug report in this message, including as much detail as you possibly can about the problem, what you did to cause it and what the local and remote machines are. If you can give a simple set of instructions to make this bug happen reliably, please include those. Thank you for helping

Re: tramp ($Id: tramp.el,v 1.440 2001/01/18 23:20:57 grossjoh Exp $); unnecessary fail while finding "file exists" command

Hi Matt I also faced the same problem. I think there should be a call to tramp-wait-for-output just after specifying the ksh prompts (or whatever shell tramp selects on your terminal). This will absorb the extra "/" generated when the prompts get specified. I included that call and never g