Clément DOUIN
Clément DOUIN
Commands `doctor`, `configure` and `synchronize` take an optional account name as parameter. If you don't give one, they will take the first account found with `default = true`. > If...
> What exactly is the use case for `default=true`? Is there really a case where I have multiple accounts, don't want to sync all of them, and also don't know...
First of all, I would advise to use the `v1.0.0` that is being tested on `master`, as it is more stable. I just updated the [installation section](https://github.com/pimalaya/neverest#installation) to make it...
> Ah I see. I was using 1.0.0-beta. I will give master a try later! If you do not want to build yourself, you can pick a pre-built release in...
Looks like an issue with the default keyring entry name generated by the config. Meanwhile you can force a specific name (if you also configured SMTP, you can use the...
I cannot reproduce the issue, could you share your configuration?
I still cannot reproduce your name issue. I placed your configuration under a `[accounts.test]` name, commented `*.client-secret.keyring` and `*.access-token.keyring` (to get default keyring names) and ran the following command: ```text...
Now at least you have a correct keyring name. Did you try to not reset entries before?
I will give another shot with my Gmail account and let you know.
The feature has been removed because it used to override the native behaviour (moving cursor inside a field). The `v4` aims to limit interactions and rely as much as possible...