I know that SO questions should have limited scope with the potential for a definitive answer. I also know that it is OK to ask a question to which you know the answer and then post an answer if the question and answer are generally useful. (Though this can also raise hackles - it can be a fine line)
My hobby is exploring the capabilities of Windows batch programming - a system with woefully inadequate documentation and loads of inconsistencies. I've invested a significant amount of timing determining undocumented features / bugs / limitations of various Windows commands. I think the info is of general use. The issue is how to get the info out there.
Would it be appropriate to ask a [batch-file] question on SO like "What are the undocumented features / limitations / bugs of the Windows FINDSTR command?" and then provide a sizeable (but manageable) answer? Or is such a question too broad?
As a developer, I know I would like a one stop shop for such info.
Well I finally posted the question and answer at What are the undocumented features and limitations of the Windows FINDSTR command?. Results have been encouraging: An initial flurry of up votes for both the question and answer within 24 hours, followed by a couple straggling up votes over the next 10 days. Thankfully, no down votes or negative comments. Not bad for a low traffic volume subject like [batch-file].
I believe the way I phrased the question post really helps to limit the scope of the answer(s) to something manageable, and discourages answers that are not truly undocumented features.