Comment 3 for bug 435780

Revision history for this message
Jonas (jonas-f-henriksen) wrote : Re: [Bug 435780] Re: Nautilus reports "could not display..." empty file

Hi Sebastian,
Yes, I understand. The problem is that the error message is not helpful at
all, and it would really seem logical to open unknown files by default in
the text editor. This is the sort of behaviour that's really annoying on
windows: each time you try to open a file that is not registered, you have
to browse through a lot of applications to find notepad to be allowed to
read a totally normal textfile.

I just installed Ubuntu 9.04 on this computer, and it seems that, now, after
I choose to open in gedit the first time, new files open fine without more
troubles. Still believe that this should be default behaviour, though :))

regards Jonas:))

2009/9/24 Sebastien Bacher <email address hidden>

> the reason it behaves differently on local and non-local locations is
> that it's using the file content on local drives to know what to use but
> it would be expensive to load the file in other cases
>
> ** Also affects: nautilus
> Importance: Undecided
> Status: New
>
> ** Summary changed:
>
> - Nautilus reports "could not display..." empty file
> + non local files opening relies on filename
>
> ** Summary changed:
>
> - non local files opening relies on filename
> + opening of non local files relies on filename to be correct
>
> --
> opening of non local files relies on filename to be correct
> https://bugs.launchpad.net/bugs/435780
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Jonas F Henriksen
Arc|Giraff AS
t 90688031