> While the particulars of your suggestions are more convoluted than they need > to be,
That's unpossible! > I think we're all onboard for mailing list support, especially with all the > ongoing suffering keeping up with this list in mail. > And, yes, this should be a plugin. Not because it shouldn't ship by default, > it should, but it's perfect dog food material for the plugin system. My point was a bit like this: If it should be turtles all the way down, then a) isn't it easier to just point out once and for all what shouldn't be a plugin but built into the core? b) isn't it about time to start defining exactly how that would work? (I've read the thread on letters-dev and it seems to have gotten lost in notification minutia, issues that are real and important, but not as important as *how should it all come together?*) Both these questions are obviously answered by isolated experimentation back and forth... but not *too* isolated! Without some guidance and eyes on the road, we'll invent mashed potatoes and build not only bookcases but in fact most of the furniture with it and will have to settle with taking solace in consistency at the expense of other things and for its own sake. And believe you me, if you're going to let me swap out fundamental commands (since you snipped, I have no idea what you responded to, but 17:46 seems to indicate that message), you have to steer explicitly towards not making everything arbitrary. /Jesper _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
