pgindent (Re: [HACKERS] LONG varsize - how to go on)
От | Peter Eisentraut |
---|---|
Тема | pgindent (Re: [HACKERS] LONG varsize - how to go on) |
Дата | |
Msg-id | Pine.LNX.4.21.9912181631110.356-100000@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: [HACKERS] LONG varsize - how to go on (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: pgindent (Re: [HACKERS] LONG varsize - how to go on)t
|
Список | pgsql-hackers |
On 1999-12-18, Bruce Momjian mentioned: > I don't need to run pgindent before _every_ release. No problem. Is this pgindent thing negotiable at all? IMHO the output of plain indent -orig looks much nicer (and readable). It also tends to look like the bsd c-style in emacs. If we could just tell people 'set up {emacs|vi|ed} like this' (such as c-set-style bsd) there wouldn't be half a dozen different formats propagating through the source until someone comes around with pgindent. Btw., I use GNU indent 2.2.1 which is a long way from the versions pgindent tries to warn about. More important than arguing about code formatting, however: Could we lose this a-tab-looks-like-4-spaces thing, now that Bruce has a new editor(?) ? In any unprepar{ed|able} viewer (cat/more/less/pico) the code looks like hell. Maybe we could lose the tab altogether because it's a pain. Just insert 4 (8, 12, ...) spaces. -- Peter Eisentraut Sernanders väg 10:115 peter_e@gmx.net 75262 Uppsala http://yi.org/peter-e/ Sweden
В списке pgsql-hackers по дате отправления: