GNOME Bugzilla – Bug 751655
Use standard::display-name for Google Drive items
Last modified: 2020-11-24 09:59:27 UTC
I have been working on a GVfs backend for Google Drive (see bug 739008). Google Drive is a database-backed storage, which means that the fundamental identifier is a cookie/blob, not a path. We create POSIX-like paths out of these IDs to fit into the GIO/GVfs world view. eg., google-drive://debarshi.ray@gmail.com/_0B9J_DkaiBDRFSHJzeTdCX1hxd3c This doesn't work well with the current strategy (in gedit_utils_basename_for_display) of using the URI to create the display title for non-local items. We need to use standard::display-name instead.
Well, that util has already some special case handling so we could add "google-drive://" as well, but the problem is that we assume to be able to call that function without blocking, but getting the display-name on a remote file is slow
(In reply to Paolo Borelli from comment #1) > but the problem is that we assume to be able to > call that function without blocking, but getting the display-name on a > remote file is slow Yeah, that is why I held back from writing a patch. We might need to move things around a bit ...
I don't like adding a special case for Google Drive, with GIO it's normally possible to use the same API regardless of the GVFS backend. The gedit utils function can be changed as an async/finish, regardless of whether it's a local or remote file.
*** Bug 756379 has been marked as a duplicate of this bug. ***
Mass-closing of all gedit bugzilla tickets. Special "code" to find again all those gedit bugzilla tickets that were open before the mass-closing: 2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3 By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements. We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.