[Syncevolution-issues] [Bug 9862] automated detection of working configuration for phone

(In reply to comment #11) > (In reply to comment #9) > > Mostly fixed, except the 'CTR+C'. Usually it hits during the syncing process, > > and SyncEvolution will suspend/abort, but the parent process has no way to know > > that the child process was ended because of user interrupt, thus continue > > testing.. > > Perhaps you could read the status.ini of the failed sync to determine whether > it completed or was aborted? There might even be a .ini file parser in Python > which groks our format. With a wrong configuration, a TransportException might throw causing SyncEvolution abort, can that be effectively differentiated from the status.ini?