dot file not synced

[xrfang]

Hi There,

Is it a known problem that dot file will NOT be synced? I try to use onedrive-d to sync an EncFS folder to OneDrive, but the .encfs6.xml file is not synced, until I copy it to encfs6.xml (removed the dot in front).

Thanks.

[xybu]

Files and folders whose name start with a dot are ignored by default (but you can edit ignore list). Note that uploading them will result in server-side error.

[xrfang]

What server side error will occur? Will errors occur in case of some particular file are uploaded (e.g. .bashrc), or ANY dot-file will cause errors? Thanks

[xybu]

OneDrive server does not allow for uploading files with name starting with a dot.

Sent from my iPhone

On Jun 22, 2015, at 1:33 AM, xrfang [email protected] wrote:

What server side error will occur? Will errors occur in case of some particular file are uploaded (e.g. .bashrc), or ANY dot-file will cause errors? Thanks

— Reply to this email directly or view it on GitHub.

[think-nice-things]

dot files do work between windows and OneDrive.

Here's my observation:

1. my setup is a windows pc and a linux pc both connected to OneDrive (the linux pc via onedrive-d)
2. I configured onedrive-d not to exclude dot files
3. create a dot file in windows, e.g. .test
4. after some time, the file is visible in the OneDrive web view with the file name Dateien.test (german settings). Note that it's not called .test in the web space.
5. after some more time, onedrive-d synchronizes the file from OneDrive and it's stored on the linux pc as .test

The only thing which doesn't work is synchronizing a dot file from linux to OneDrive.

Any ideas?

[ewann]

I haven't tested potential impact of the comments I'll make:

Have you reviewed ignore_v2.ini? By default it includes .* which I think will match the files you are questioning. You might find removing that exclusion solves your problem, or that all your data is lost ;)

If you attempt this (using a test account or otherwise) please do feedback your findings - the previous comment by xybu suggests this may be a limitation with the currently used api