On Thu, 5 Aug 2010 18:19:19 +0100, Jake wrote:
On Thu, Aug 5, 2010 at 1:01 PM, Lex Trotman elextr@gmail.com wrote:
Clearly Glib is not going to be fixed and there is some consideration being given to making the GIO file handling available in Geany if the system it runs on supports it, but someone has to have the time to do it.
Well, it's not really GLib what Geany uses for file IO, it's rather libc. So, what's happening when you save a remote file via SSH in Geany is that a simple write operation if performed on a file in the filesystem. Pretty much the same as a simple 'cp' on the command line. The remote file is mounted into the filesystem using GVfs and its fuse backend which actually outs the remote end into the filesystem. That works mostly transparently for the users so you don't notice a bit difference between apps like Geany and Gedit. Gedit instead doesn't use good, old libc, they use the new GIO API which directly communicates with the remote end through GVfs.
So, now we know what's going on. No doubt, the indirection through the fuse filesystem doesn't speed up things. Still I'm wondering why it seems so much slower to you than Gedit's saving. Can you try to do some tests on the command line with 'cp' and 'gvfs-cp', 'cp' uses libc, 'gvfs-cp' uses GIO.
Slighty OT, but is there a way to actually _pay_ a developer to do the
I won't participate in this discussion. I personally don't like paid features very much but this is just me.
Regards, Enrico