Ok, I can now confirm this and I believe I know the source of the issue.
The problem occurs with shell scripts, python scripts, ruby scripts, and
possibly others.
Basically, Wine is (correctly) associated with MIME type
"Application/x-executable", since this covers some .exe files (including
non-Windows ones generated by Winelib). shared-mime-info classifies
shell, python, and ruby scripts as sub-classes of
application/x-executable, so anything that can open x-executables is
used to open the scripts (in this case Wine). Since "sub-type of
executable" is listed before "sub-type of text file" for scripts,
handlers for executables (Wine) show up before handlers for text files,
and thus Wine gets used to open it.
One possible fix is to get rid of the sub-typing in shared-mime-info.
It's unlikely anything that could open "executables" should also be
opening python/ruby scripts in this way (in fact Wine is probably the
only program associated with executables at all). Another possible
workaround is to just switch text/application so that the default
becomes the text editor handler, but this leaves the problem with Wine
still being listed as a handler for something it isn't.
** Changed in: wine (Ubuntu)
Importance: Undecided => Medium
Status: Incomplete => Confirmed
** Also affects: shared-mime-info (Ubuntu)
Importance: Undecided
Status: New
--
wine wants to open shell scripts
https://bugs.launchpad.net/bugs/192122
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shared-mime-info in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
