Re: tramp-gvfs: parsing issues when using locale

[Jürgen Hötzel]

Hi Michael

On Tue, Oct 13, 2015 at 9:58 AM, Michael Albinus <address@hidden> wrote:

Please do. Better would be to use "en_US.utf8" or "C.utf8". See also
`tramp-get-remote-locale' in tramp-sh.el.

Furthermore, pls don't set it globally in `process-environment'. I did
something similar in tramp-sh.el; afterwards people were annoyed not to
see their preferred date format in dired, for example. Maybe you could
set it like "env LC_ALL=... LANGUAGE=... gvfs-info" in
`tramp-gvfs-handle-file-attributes'.

 

Done.  `process-environment' is dynamic bound there, so this should not have any impact on

other uses of `process-environment'. 

Btw, I'm curious what you plan with google-drive backend and
tramp-gvfs.el. A while ago I was thinking about adding a "gd" method,
but there was no time / not enough motivation yet to start with.

It's not a specific google-drive backend. Just another gvfs-backend:

You need to install gvfs-google and gvfs-goa (Google online accounts). Of course you have to setup your Google online account in Gnome 3.18.

It already works for me. The only problem is the  non-posix-semantic of Google Drive paths (https://debarshiray.wordpress.com/2015/09/13/google-drive-and-gnome-what-is-a-volatile-path/):

Each file is identified by a unique blob-id and not by its path. So users justs see the blob-id's in directory listings.

Tramp-gvfs could use the file-attribute

display name: IMAG0260.jpg

(like its done in the gnome file browser Nautilus) to translate between display-names and the blob-id. What do you think about it?

Regards, 

​