Find a better name for `neverest configure`

[soywod]

The configure command is misleading. It can be interpreted as "configuring an account in the config file". Actually it configures an already existing account at the application level (set up keyring, folders etc).

[shymega]

What about configure ---add to add new accounts through the wizard flow? I really liked the wizard.

[soywod]

Adding account to existing configuratio should be fairly easy. Editing is trickier and I prefer to leave it to a dedicated tool. The real concern is how to properly split config commands: one for configuring an account at config file level (the actual wizard) and one for configuring an account at app level (the actual configure command).

We could have sth like:

• neverest config wizard to start the wizard. If the given -c|--config (or the default path) points to a valid config file, it will just append the new config
• neverest config keyring to configure the keyring system for the given account
• neverst config <item> is open for future stuff to configure
• neverest doctor to check that config file is ok, that all is configured

[shymega]

I agree on most of your points.

However, I wonder if something like neverest init for the first-time setup, neverrest init keyring $ACCOUNT/neverest init keyring --all, and so on.

It feels more ergonomic with the above, and init could be shortened to i- a la NPM.

What do you think?