It should be easy to implement it:
- The unique plugin's functionality may or may not be an option.
- But the duplicated functionality (which is present in tracopt too) must be an option for the plugin, I think.
That would allow one choosing between the tracopt and plugin for the duplicated ticket-comment-update functionality.
It probably should be categorized as defect rather than as an enhancement.
I've tested that both tracopt's and the plugin's listeners can be enabled and both can work in the same time.
You've made a very useful tool and I really like that Ticket-Changeset list box!
However I still hesitate using it in our production environments (because of yet lacking un-reformat functionality) but if the proposed here option was implemented, I'd go installing it immediately.
BTW: Speaking honestly, I can't understand why you've cloned the existing tracopt functionality too instead of getting only what you really need from their code?
IMHO it would be better if the plugin was kept as simple as possible, doing only its unique things (and concentrate on making it do just these things as better as possible). For example if you implemented only the plugin's unique features then you wouldn't need any "diff" and "reformat" commands too.