> Assuming you want to set up a separate notmuch database to test you do
> the following:
>
> first:
>    get a client secret API key for gmailieer [0], you only need this
>  during setup or if gmailieer needs to be re-authenticated. so store it
>  somewhere safe, say: ~/.secret/client_secret.json. ideally this should
>  be unnecessary [1].
>
> # setting up a separate notmuch db
> $ mkdir ~/test_mail/  # our new mail root
> $ cd ~/test_mail
> $ export NOTMUCH_CONFIG=$(pwd)/.notmuch-config
> $ mkdir mail          # new mail database root
> $ notmuch setup
>  * specify ~/test_mail/mail as mail database
>  * specify only 'new' as new tag
> $ notmuch new         # create db
> $ cd mail
>
> NOTE: As long as you are using a non-standard notmuch config location make
> sure that environment variable is set when using gmailieer.
>
> # setting up gmailieer
> $ mkdir gmail
>  * this will be the gmailieer local repository.
>  * it should be a sub-dir of the root mail db.
>  * you can keep other mail (from other accounts) outside this
>    gmailieer local repository.
> $ cd gmail
> $ gmi auth -c ~/.secret/client_secret.json
>  * authenticate gmailieer, choose the correct account, say:
>    charlie.root@gmail.com
> $ gmi init -a charlie.root@gmail.com # gmailieer should now be set up
> $ gmi pull # does the initial pull, fetching all you messages - this
>           # could take some time.

It is currently running. Thank you so much.

The only things I noticed so far:

* running auth before init fails, but running init -c ... -a ... works
* I had to name the auth file client_secret.json or "gmi pull" would
fail trying to read it.

Thanks again for writing this. It seems a much better way to sync with
gmail. My previous setup was to use mbsync. It is really fast for
fetching new emails (--pull-new), but with imap the only way to get
flag changes (including read/unread) seems to be to ask for the flag
of every message!

Cheers,
Rafael