On Mon, 2014-10-06 at 10:44 -0700, Todd Wilson wrote:
> "username=goa:..." is in google/peers/target-config/config.ini and not
> in any of the other config.ini files.

Nevertheless, can you show the output of:

syncevolution --print-config -q google
syncevolution --print-config -q target-config@google

In addition, repeat the exercise with locating the error. This time,
let's catch both throws and the function:


SYNCEVOLUTION_DEBUG=1 gdb --args syncevolution --daemon=no --sync
refresh-from-local google
# b SyncEvo::IdentityProviderCredentials
# catch throw
# run
...
# where / cont

> As for your question about the error message, I would opt for an
> approach that attempts to maintain the semantic integrity of the
> configuration files. If that value in the username field semantically
> shouldn't be there, then I think at least a warning would be given.

You are right, warnings are under-utilized. That would be a good option.

> Stronger options would be (1) to give the user an option (via a
> prompt) to remove the value from the configuration, or even (2)
> silently remove it automatically. It should be ignored only if it is
> semantically consistent for it to be there.

Editing the config is hard. The command line tool is only one of several
ways how the user might run a sync, so any solution that only works for
the command line (and only when run interactively) would be incomplete.
OTOH, only users of the command line are likely to end up with wrong
configs.

I don't like rewriting the config without user confirmation. There's
always the possibility that the user wanted it to be that way and an
automatism makes things worse.

-- 
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]
https://lists.syncevolution.org/mailman/listinfo/syncevolution

Reply via email to