Anon monk here, but not the OP.
Note to developers: if I ask you a question, I've read the docs and am not able to find the answer. Maybe it's in there or maybe it isn't, but I can't find it (which means others may also have trouble finding it). If
then I'm apt to fix that one little piece of the docs myself and nudge you to accept the changes.
My advice: please make your repo available, and when you answer a question (please do!), if you don't think you can make the time to update the docs yourself, encourage the askee to improve your docs themselves.
Aside: if you don't know the answer to a well-researched and courteous question, please say so! An, "I've got no idea, never tried it" or "tried that once in a previous version and it was an awful idea" or "please ask on the mailing list" is far better than no reply at all. No reply at all makes me think maybe you're either rude, or don't maintain the code anymore, or maybe the email I sent is stuck in limbo somewhere.
In reply to Re: Sometimes, just saying "Thank You" is not good enough
by Anonymous Monk
in thread Sometimes, just saying "Thank You" is not good enough
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |