InformAction Forums

NoScript CHANGELOG
[...]
v 1.10
==========================================================================
+ ABE built-in ruleset editor

How would I access this built-in editor? When I edit my ABE rules, NS still launches Notepad.

It just means you can edit the rules in places now (without hitting the "Edit" button), rather than launching an external editor which still remains an option.

Not sure as of when, but (even latest NoScript version) at some point the Edit button on the ABE options menu stopped launching the given SYSTEM or USER rules in the editor previously configured with the noscript.abe.editor preference. Instead of pulling up (on Linux) /usr/bin/gvim (or even just gvim) like it used to, it seems to completely ignore noscript and want to launch C:\windows\system32\notepad.exe from within Wine.

Did the abe editor pointer get removed or lose priority in deciding to open one of the rule files? kind of at a loss here, I'd prefer the noscript.abe.editor choice to be priority when hitting the Edit button on the ABE options menu rather then having to rely on just the built-in ABE editor (which btw, thanks for implementing that too, its great for quick edits without having to launch an
editor even though it lacks some depth, keeping it simple is best though)...

thanks in advance...

piker wrote:Not sure as of when, but (even latest NoScript version) at some point the Edit button on the ABE options menu stopped launching the given SYSTEM or USER rules in the editor previously configured with the noscript.abe.editor preference. Instead of pulling up (on Linux) /usr/bin/gvim (or even just gvim) like it used to, it seems to completely ignore noscript and want to launch C:\windows\system32\notepad.exe from within Wine.

Please check whether Notepad is currently configured as the handler for the "application/x-abe-rules" mime type or the ".abe" file extension either at the OS level (does Wine maintain is own Windows-like file associations registry?) or in Firefox's File|Preferences|Applications.

I don't know where or how the mime-type application/x-abe-rules would have been introduced into any of the Linux or GNOME mime types (yet) .. but yeah, I thought of looking under the helper applications too (I'm running Seamonkey btw, 2.0.9 now) ...
I suppose its possible that a Wine install somehow took priority over unknown mime-types, except I haven't seen anything similar happen with other unknown types...

Ultimately, if I need to, I can add the mime type and association at system level and/or under helper apps in the browser.. Does this mean that the configurable ABE external editor preference was actually dropped though or what?

Thanks for the quick response as usual btw!

In Windows, if you click on an unknown file type (which an .abe is initially), you are prompted for the application to use to open it with. (Win32pad in my case.) You can then save that as the default handler. (There are no settings within SeaMonkey Preferences pertaining to "abe".)

Linux have similar?

[quote="therube"]In Windows, if you click on an unknown file type (which an [i].abe[/i] is initially), you are prompted for the application to use to open it with. (Win32pad in my case.) You can then save that as the default handler. (There are no settings within SeaMonkey Preferences pertaining to "abe".)

Linux have similar?[/quote]

Unfortunately nope, neither. I apparently have to edit /etc/mime.types and/or /etc/mailcap or add the mime type manually to Seamonkey's mimeTypes.rdf

therube wrote:In Windows, if you click on an unknown file type (which an .abe is initially),

File endings play much less of a role in most unixoid OS.