I'm trying out the sftp plugin and have a problem.
I set up an sftp account and can open a file on a remote machine (beagle bone running debian linux) just fine. But when I try and save it, it's just saved to the local machine under
C:\Users\dasfoo\AppData\Roaming\CodeLite\sftp\tmp\HelloBastages.c and it doesn't get sync's to the remove machine.
Any pointers? I was running codelite 7.0 but upgraded to 8.2.6 hoping it was an already fixed bug or something, but no luck. Saving the file does nothing. And there doesn't seem to be a 'sync remote file' anywhere either.
???
Saving a file opened with sftp
-
- CodeLite Expert
- Posts: 167
- Joined: Fri Jul 22, 2011 5:32 am
- Genuine User: Yes
- IDE Question: C++
- Contact:
- eranif
- CodeLite Plugin
- Posts: 6375
- Joined: Wed Feb 06, 2008 9:29 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Saving a file opened with sftp
The file should be saving automatically to the remote path if it was opened with the sftp plugin to begin with
i.e the flow is:
- Open the remote file via the SFTP plugin
- Edit the file
- Save
If you close the file and then re-open it from the local copy, CodeLite will not sync it again
To confirm that the file was uploaded, you can check the "SFTP" tab in output view
Eran
i.e the flow is:
- Open the remote file via the SFTP plugin
- Edit the file
- Save
If you close the file and then re-open it from the local copy, CodeLite will not sync it again
To confirm that the file was uploaded, you can check the "SFTP" tab in output view
Eran
Make sure you have read the HOW TO POST thread
-
- CodeLite Expert
- Posts: 167
- Joined: Fri Jul 22, 2011 5:32 am
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: Saving a file opened with sftp
I tried this on a different target and it worked as expected.
If I figure out why it wasn't working on board I was given to test I'll update. Currently suspect that it's failing maybe because NTP isn't working correctly so the time on the target machine (beagle bone black) is way off. It thinks it's March 23, 2015.
Edit: Pretty sure it's not due to NTP.
If I figure out why it wasn't working on board I was given to test I'll update. Currently suspect that it's failing maybe because NTP isn't working correctly so the time on the target machine (beagle bone black) is way off. It thinks it's March 23, 2015.
Edit: Pretty sure it's not due to NTP.