From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
File-roller should use the Gnome default text editor when an item in
an archive is double-clicked.
Currently it launched emacs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Works for me on rawhide (file-roller is 2.8.1). If you can still
reproduce please reopen and specify:
- What editor is used to open the file, what is your default text
editor and how you configured it
- What nautilus does on the same (unarchived) file
If the file is a perl script, with the extension .pl, emacs opens.
My default text editor (in gnome) is gedit.
If a "proper" editor is going to be opened rather than a simple text
editor, maybe there should be a preference for that.
Do you want this reassinged to gnome, or to the preferred-apps program?
Following this link using epiphany also opens emacs:
The content type is text/txt.
*** Bug 137295 has been marked as a duplicate of this bug. ***
The problem with perl files is user interface unintuitiveness ihmo.
The Text Editor tab in preferred applications is confusing. You can
use nautilus properties to change the editor for perl files.
I'm confused about the issue with epiphany. Unless you have text/txt
handler set, it should just use the text/plain handler which is the
one that open normal text files in nautilus (so gedit for you). Could
you test that with a clean user please ?
This is about the user interface problem:
Tested with a new user. Same problem.
Also a new problem- using the new account, clicking the web browser icon tried
to install firefox, which isn't installed. Euck.
Ok, this is a bit of a pain. I think the correct fix is to add an
alias to shared-mime but first we need to improve gnome-vfs alias support.
application/rtf opens with emacs too. Nice!
Marco, the upstream xdgmime sources provide alias subclass information
now, you should get that for free when you update the xdgmime in gnome-vfs
I think this is all fixed upstream. It required large changes,
included API, so I dont think we can release updates to fix it.