Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> If it were "the else's indent plus one more tab" it would be reasonably
> >> sane; it'd match the indentation of what comes next.
>
> > OK, I can do that but consider:
> > [ other case ]
>
> Just out of curiosity
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> If it were "the else's indent plus one more tab" it would be reasonably
>> sane; it'd match the indentation of what comes next.
> OK, I can do that but consider:
> [ other case ]
Just out of curiosity, what will pgindent do when re-ru
Bruce Momjian <[EMAIL PROTECTED]> writes:
> and this does exactly as you describe by putting the comment on its own
> line. I just changed it to:
> ...
> so that the new comment will have the same indenting as the else that
> was input.
If it were "the else's indent plus one more tab" it would be
Tom Lane wrote:
> This case in xlog.c is representative of a disease that pgindent has had
> for awhile:
>
> @@ -4276,7 +4300,8 @@ StartupXLOG(void)
> if (needNewTimeLine)/* stopped because of stop request */
> ereport(FATAL,
>
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > and this does exactly as you describe by putting the comment on its own
> > line. I just changed it to:
> > ...
> > so that the new comment will have the same indenting as the else that
> > was input.
>
> If it were "the else's inden
This case in xlog.c is representative of a disease that pgindent has had
for awhile:
@@ -4276,7 +4300,8 @@ StartupXLOG(void)
if (needNewTimeLine)/* stopped because of stop request */
ereport(FATAL,
(errmsg("request
