Re: Proposal: new border setting in psql
От | Bruce Momjian |
---|---|
Тема | Re: Proposal: new border setting in psql |
Дата | |
Msg-id | 200901081805.n08I53E04514@momjian.us обсуждение исходный текст |
Ответ на | Re: Proposal: new border setting in psql (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Proposal: new border setting in psql
|
Список | pgsql-hackers |
Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > Yes, I did, and now I see why you said there might be only a few broken > > cases. But I did not see any documentation in the standard saying that > > was OK: > > http://docutils.sourceforge.net/docs/user/rst/quickref.html#escaping > > The example on that page is just bizarre. If the first asterisk > has to be escaped to prevent it being taken as markup, why doesn't the > second have to be? I suppose it's because there's no "closing" asterisk > to match it, but that's not the sort of thing one ought to depend on. So what would this show? \*escape* \*escape* Want to bet the second word it italics. > > so it might be that your ReST interpreter is broken. > > Looking at this I'd say the ReST standard is broken, or at least expects > unreasonably complicated behavior. But anyway, it's quite clear that > there are *many* cases that need escaping, not only backslashes. Yea, there doesn't seem to be enough information on that page to form a standard behavior. Ah, OK, here is where we should be looking: http://docutils.sourceforge.net/rst.html#reference-documentation URL updated on TODO list. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-hackers по дате отправления: