On Wed, 2009-11-25 at 08:33 +0000, Jussi Kukkonen wrote: > Patrick Ohly wrote: > > Should we change the semantic of the D-Bus API so that this is done > > automatically? It would force users of the API to set it explicitly to 1 > > when wanted (command line?) and disable the user's configuration option > > (unless the D-Bus client checks the config first itself). > > Setting printChanges=0 in the client is not a big deal, but defaulting > to 0 (however that technically happens) in the D-Bus case makes sense to > me... I wouldn't expect a service to spend a lot of time outputting to > stdout.
Except when the client is the command line and we implement #5042: D-Bus API: send log output to clients... That would include the output of synccompare. For the sake of a clean design, would you mind setting printChanges=0 yourself? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
