pgindent (Re: [HACKERS] LONG varsize - how to go on) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject pgindent (Re: [HACKERS] LONG varsize - how to go on)
Date
Msg-id Pine.LNX.4.21.9912181631110.356-100000@localhost.localdomain
Whole thread Raw
In response to Re: [HACKERS] LONG varsize - how to go on  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: pgindent (Re: [HACKERS] LONG varsize - how to go on)t
List 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 by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Anyone for prettyprinted EXPLAIN VERBOSE?
Next
From: Bruce Momjian
Date:
Subject: Re: initdb.sh fixed