Thread:Mathmagician/@comment-3508190-20120619000730/@comment-4674838-20120821204049


 * Configuration options would cause a mess when both are present and there's a conflict...


 * 1) I believe global.js always loads *AFTER* site-wide JavaScript files -- this has always been my experience, and is expected behavior. I see no reason not to use this fact to force user config options to override site-wide config options.
 * 2) *If I am wrong about this, you could just provide 2 different config objects. Force admins to use one for site-wide. Force users to use a different one for user-specific. And then have your script  everything appropriately so that user config options win out.
 * 3) For CSS, users can simply use  to override site-wide CSS. That is, after all, one of the very purposes of

This is just more of a general thing though. For Find+Replace itself, I definitely agree with removing all config options. Find+Replace is a small utility that should be compact and consistent, not some confusing, large entity with different configurations...