On 12/14/16 5:12 PM, Stephen Frost wrote: > For my 2c, at least, because we're going to be constantly fighting with > the trailing whitespace in those examples. If you forget to s/</</g, > the docs aren't going to build and it's going to be extremely obvious > that you need to do something. Not that I'm actually happy about that- > I'd much rather tell the doc engine "copy this verbatim until you see a > </closeverbatim> tag" or whatever, and not have to go hack up psql > output at all,
This already exists: git grep -w CDATA > That said, if we can make git complain about trailing whitespace in the > docs but not mind it in the regression test output, then at least most > will hopefully realize that they need to go through and strip out the > trailing whitespace before committing. That would be easy to do. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
