search

Grive / grive

an open source Linux client for Google Drive
http://www.lbreda.com/grive/start
GNU General Public License v2.0
1.59k stars 378 forks source link

.When using grive with -p option, .grive_state is put in working directory and not the google drive directory #285

Open DaveDeCaprio opened 10 years ago

DaveDeCaprio commented 10 years ago

It seems that grive is always creating the .grive_state file in the current working directory, even when the -p option is set. The .grive file is correctly placed in the target directory with -p, but .grive_state isn't.

softbaer commented 9 years ago

Hello,

i have the same problem. May be i started grive on two linux-machines?

DaveDeCaprio commented 9 years ago

I think I fixed this by updating grive to the latest version.

Dave

From: softbaer [mailto:notifications@github.com] Sent: Tuesday, April 21, 2015 9:09 AM To: Grive/grive Cc: David DeCaprio Subject: Re: [grive] .When using grive with -p option, .grive_state is put in working directory and not the google drive directory (#285)

Hello,

i have the same problem. May be i started grive on two linux-machines?

— Reply to this email directly or view it on GitHub https://github.com/Grive/grive/issues/285#issuecomment-94808309 . https://github.com/notifications/beacon/AAzVupeUEAmK7N88TIh4lMBVwvF7icxJks5oBlFkgaJpZM4C4d-_.gif

softbaer commented 9 years ago

thank you.

Am 21.04.15 um 16:11 schrieb David DeCaprio:

I think I fixed this by updating grive to the latest version.

Dave

From: softbaer [mailto:notifications@github.com] Sent: Tuesday, April 21, 2015 9:09 AM To: Grive/grive Cc: David DeCaprio Subject: Re: [grive] .When using grive with -p option, .grive_state is put in working directory and not the google drive directory (#285)

Hello,

i have the same problem. May be i started grive on two linux-machines?

— Reply to this email directly or view it on GitHub https://github.com/Grive/grive/issues/285#issuecomment-94808309 . https://github.com/notifications/beacon/AAzVupeUEAmK7N88TIh4lMBVwvF7icxJks5oBlFkgaJpZM4C4d-_.gif

— Reply to this email directly or view it on GitHub https://github.com/Grive/grive/issues/285#issuecomment-94809303.