On Wed, Apr 15, 2009 at 3:58 PM, Michael Albinus <[email protected]> wrote: > Adam Jenkins <[email protected]> writes: > >> This should be it. >> >> 13:29:27 tramp-send-command (6) # test -e /usr5 2>/dev/null; echo >> tramp_exit_status $? >> 13:29:27 tramp-get-connection-property (7) # process-name nil >> 13:29:27 tramp-get-connection-property (7) # chunksize 0 >> 13:29:27 tramp-set-connection-property (7) # last-cmd-time (18918 10119 >> 90742) >> 13:29:27 tramp-get-connection-property (7) # process-buffer nil >> 13:29:27 tramp-get-connection-property (7) # check-remote-echo nil >> 13:29:27 tramp-get-connection-property (7) # check-remote-echo nil >> 13:29:27 tramp-get-connection-property (7) # check-remote-echo nil >> 13:29:27 tramp-get-connection-property (7) # check-remote-echo nil >> 13:29:27 tramp-wait-for-regexp (6) # >> >> ///b51aada9386d36a14411ba28076ef9a5 > > Strange. Here, the return code of the test command shall be visible. > > Could you apply "M-x tramp-cleanup-all-connections" before the next test?
I would like to note that it started on me again, and this fixed it the second time. > > Best regards, Michael. > _______________________________________________ Tramp-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/tramp-devel
