same-exports-dir doesn't seem to work

[alienth]

When using drive pull --same-exports-dir -export txt, drive seems to create blank files and then try to mkdir over top of them. For example:

$ ls
$ drive ls
/foo/bar
$ drive pull --same-exports-dir -export txt
Resolving...
+ /foo/bar
Addition count 1
Proceed with the changes? [Y/n]: y
pull: /foo/bar err: mkdir /home/alienth/gdrive/foo/bar: not a directory
$ ls
bar  bar.desktop

The created bar file is empty, while the doc up in drive is not.

This seems to occur regardless of the export format requested. I'm using the latest drive as fetched from go get a few hours ago.)

[ikwyl6]

any chance if this getting looked at?

In order for drive to export the 'Google' files to a xls/xlsx/pdf/etc as per similar cmd from above OP, you have to specify the -exports-dir flag but then it will export all nested files within one specific folder (no the -same-exports-dir folder) and then you have to manually move all the exported files that got exported to -exports-dir to their respective dirs that could be nested/down/the/tree.. A lot work!