Some patches, some ideas.

[LemonBoy]

This makes grive behave a bit better.
The resources shouldn't assume that "." is the path base to make the whole system flexible enough to make libgrive (and grive) useful. If the source Drive is stored into the Resource then you could build the full path by just appending the drive m_state path and all the parent names.

[nestal]

Why should we move .grive to the home directory? I want to have one .grive file in every directory the user sync with Google Drive. A user can have multiple directories which contains multiple .grive files.

[LemonBoy]

It's not advised to clutter every directory, having a single database would be better.

[nestal]

Many thanks for the patch. I merged but reverted 9a76cb8 in my branch.

I have adjusted the indentation. I used tab characters instead of spaces. I hope you can follow.

We can continue our discussion on why we want to move .grive to $HOME.

[nestal]

Some people have multiple google accounts and multiple google drives, they may have multiple directories to sync and need different access tokens. That is why grive uses multiple .grive files in different directories.

[LemonBoy]

Use a single config file and let the user define in there the drives and the folder that should be synced/watched for each drive. Something like

{
    "Drive1" : {
        username : "herp@gmail.com",
        pass : "derp",
        folders : [ "~/google", "/steals/my/data", "/while/i/sleep" ]
    },
    "Drive2" : {
        username : "derp@gmail.com",
        pass : "herp",
        folders : [ "~/p0rn" ]
    },
}

A much saner approach than syncing the cwd :)

[nestal]

That's a good idea! You want to write the code for it?

[LemonBoy]

Libgrive should be adjusted to not assume the cwd (".") as resource root but using the parent drive folder instead.
Anyway I'm no c++ coder but should be quite easy given a robust json parser :)

[nestal]

Grive is using json-c right now. See libgrive/src/protocol/Json.cc