Find_enclosing_mountpoint docs don't match reality


From the docs:

find_enclosing_mount(cancellable = nil)

Gets a GLib::Mount for the GLib::File.

If the file doesn’t have a mount (for example, possibly a remote

share), a GLib::IO::NotFoundError will be raised.

This would imply that remote shares don’t have a mountpoiont. The
opposite is observed:

$ irb -rubygems -rgio2
irb(main):001:0> local = GLib::File.new_for_commandline_arg
=> #<#Class:0x7f79e3627f50:0x7f79e3627e88 ptr=0xdc88c0>
irb(main):002:0> remote = GLib::File.new_for_commandline_arg
=> #<#Class:0x7f79e361ce98:0x7f79e361cdd0 ptr=0xde9e70>
irb(main):003:0> local.find_enclosing_mount
GLib::IO::NotFoundError: Containing mount does not exist
from (irb):3:in find_enclosing_mount' from (irb):3 irb(main):004:0> remote.find_enclosing_mount GLib::IO::NotMountedError: The specified location is not mounted from (irb):4:infind_enclosing_mount’
from (irb):4

On Fri, Sep 9, 2011 at 15:31, Michal S. [email protected]

opposite is observed:
I don’t understand what you mean.

I would suggest that you take this to the gtk-devel mailing list, as I
suspect that this is behavior dictated by GLib, not Ruby-GNOME2.