I didn't contact the maintainer, it should be responsibility of him/her to be responsive to patches.
His address on the syntax file is wrong anyway. He eventually replied, years later, not looking at my patches, and he didn't reply to me so I never got that response. He said he didn't read every mail in the mailing list (even though all he needed to do is read the sh syntax mails), presumably implying that he wanted to be CC'ed, but then he doesn't CC me, so the only way I could have read his response is to be constantly checking the mailing list for two years. And the comment I made was not about the content of the code, certainly not about the content of the sh syntax file, it was about the development **PROCESS**. The current content of the code is almost irrelevant, as the project with the better development **process** will eventually have better code. So my comment was true, it's just that you are not listening to what I'm actually saying. And BTW it was a miracle I saw this mail, as I saw it from the web interface. I'm a member of this group but I don't receive mail from it. I guess there isn't a habit of replying to the person you are actually replying. I'm not trying to be snarky, I'm just trying to to illuminate the fact that my experience as a random patch contributor has been anything but smooth. I contribute to many projects and rarely do I experience such issues. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/b52a1c5e-c144-4fc4-9270-6f2895b81be8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
