Comment 5 for bug 86233

Currently, my real problem seams to be this: I cannot open a (bash) file with gedit through Nautilus.

First try: double click. Because Nautilus has no knowledge about the file type, this is the error message I get: "Cannot open ssh://root@192.168.0.201/usr/local/sbin/3a-transcode: No application suitable for automatic installation is available for handling this kind of file.". This can be considered as normal because of the unknown file type.

Second try. Make a file association to this file: Right click, Properties, Open with, Add, Select 'Text editor'. This does not work because the selected program cannot be added, probably because the file type is unknown. Error message: "Could not add application to the application database". This can be considered as normal because of the unknown file type.

Third try. Right click, Open with another application, select 'Text Editor'. I get the same message as when I'm trying to change the file association (see second try): "Could not add application to the application database". This cannot be considered as normal because I want to open the file only *this* time with the selected application.

Fourth try. Open gedit, browse to the ssh'ed file and open it. This works.

My guess that this is my problem: just because Nautilus cannot add the application due to the unknown filetype, blocks me from opening a file with a application of my choice. Ofcourse, if SSH gives the correct file types back, this problem is not likely to exist.

Note. This optimization which you mention is for SSH connections only? When connecting through Samba (static mount of gnome-vfs), file types are (normally) read.