Niklas Gollenstede

First off: This should already work, since reStyle only edits/adds its own section in the `userChrome.css`. Install that theme (by copying); restart Firefox or disable/enable chrome styles in reStyle, which...

There is a good very good chance that updating to [NativeExt 0.2.1](https://github.com/NiklasGollenstede/native-ext/releases/tag/v0.2.1) fixes that. You should not need to register reStyle again. Just restart it after the installation of NativeExt....

NativeExt needs to find the installation of the extension on the disk. That can be very tricky. With Firefox, it relies on the `MOZ_CRASHREPORTER_EVENTS_DIRECTORY` env var to point to a...

Okay. Please try this: * use the System Monitor or whatever tool you have installed to find the pid of the running Firefox process * run `xargs -n 1 -0...

The security concept of NativeExt is that it finds the extension installation itself. That way (unless a file in the extension calls `eval()`) it can make sure that only the...

> neither even use xargs The `xargs` in `xargs -n 1 -0 < /proc//environ` only formats the content of `/proc//environ`. Otherwise, it is not related to the env vars. >...

It doesn'T really matter if the folders actually exist. NativeExt simply reads the env var and assumes that the root of the profile folder is two directories up. If you...

>> It doesn'T really matter if the folders actually exist. >> You can either create the folder and put css files in it, change the preference on the options page...

> > From userstyles.org I just found this which uses @namespace, but doesn't apply for some reason. Maybe because of "advanced settings"? > reStyle supports `userstyle.org`s style settings, that shouldn't...

Havn't considered it yet, but I'd like to make some changes to the style installation anyway. A preview would be nice, with direct options to change the style settings. A...