killing and restarting a dialup connection

2000-06-25 Thread Francesco Potorti`
I use tramp 1.393 from home, using a dialup connection. Here in Italy, quite often you pay your Internet connection per minute, so it often happens that I close the PPP session, and reopen it some time later. I often (always?) observed problems when using tramp like this: - open

moveing a remote file to a local directory

2000-06-25 Thread Francesco Potorti`
Using tramp 1.393, I moved (using dired) a remote file to a local directory. The file was indeed copied to the local dir, but the remote one was not deleted.

Re: killing and restarting a dialup connection

2000-06-25 Thread Kai Großjohann
Francesco Potorti` [EMAIL PROTECTED] writes: I use tramp 1.393 from home, using a dialup connection. Here in Italy, quite often you pay your Internet connection per minute, so it often happens that I close the PPP session, and reopen it some time later. I have tried to make Tramp

Re: killing and restarting a dialup connection

2000-06-25 Thread Francesco Potorti`
I use tramp 1.393 from home, using a dialup connection. Here in Italy, quite often you pay your Internet connection per minute, so it often happens that I close the PPP session, and reopen it some time later. I have tried to make Tramp recognize what's happening; see the

Re: killing and restarting a dialup connection

2000-06-25 Thread Kai Großjohann
Francesco Potorti` [EMAIL PROTECTED] writes: In fact, it seems to be reproducible. Here is a backtrace. Signaling: (quit) accept-process-output(#process *tramp/rsync pot@fly* 1) tramp-wait-for-output() tramp-handle-file-exists-p("/r@rsync:pot@fly:/home/pot/tmp") Okay.