I agree that the plugin system could bear some modifications.
- A Firefox plugin system will be a pleasure but I'm afraid of the work load.
- A file with a package loading sequence was my first idea. But I don't think this will be very comfortable. Loading Plugins on demand (and with them the referenced packages) may be a solution to discuss. It may slow down editing on the first usage of the plugin.
- Overriding of key binding should be independent from the loading sequence of the plugin. The solution of other editors to present a list of commands bound to the key pressed is not an option. Overriding is good. It makes it easy to change the bindings. I propose an overriding convention: [list][*]first load the default keymap,
- then load package keymaps in random order
- at last load user keymap.
Two or more packages scramble for a key. The user should notice if the editor does something surprisingly. The user is asked to customize the user keymap.[/*:m]
[li]I've used bundle editors and I don't think this will be a good way to go. I already edit the plugins, language files and keymaps in ST. Making a package a project is it. [/li][/list:u]