On Fri, 2 Jun 2000, Kai Großjohann <[EMAIL PROTECTED]>
wrote:
> "Mark A. Hershberger" <[EMAIL PROTECTED]> writes:
>
>> $ tramp_test_nt () {
>> test -n "`find $1 -prune -newer $2 -print`"
>> }
>> # Looking for remote executable `/bin/perl5'
>> $ test -x /bin/perl5 ; echo $?
>
> I got that (`End of file during parsing'), too, and it happened at the
> same spot. But debug-on-error didn't catch it.
>
> Does anybody know what's going on?
I think that it is a bug in `tramp-run-test', or maybe
`tramp-wait-for-output'.
Simply put, it looks like wait for output fails (for some reason) to
strip away the '/////' bit of the text, and point is left in the wrong
place.
Point then moves to '(point-max) (forward-line -1)' which leaves it on a
blank line.
Then the reader is invoked and fails to read anything.
I didn't get any further in working through it, but I think that it's
the wait for output stuff. OTOH, maybe the 'run-test' could act like:
(goto-char (point-max))
(search-backward-regexp "^[01]$")
This would make the location of the status report more robust, against
errors in the output.
Daniel
--
The desire to belong is partly the desire to lose oneself.
-- Eric Hoffer
