pgindent vs. pgperltidy command-line arguments

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: pgindent vs. pgperltidy command-line arguments
Date: 2023-05-25 09:10:48
Message-ID: 45aacd8a-5265-d9da-8df2-b8e2c0cf6a07@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Until PG15, calling pgindent without arguments would process the whole
tree. Now you get

No files to process at ./src/tools/pgindent/pgindent line 372.

Is that intentional?

Also, pgperltidy accepts no arguments and always processes the whole
tree. It would be nice if there were a way to process individual files
or directories, like pgindent can.

Attached is a patch for this.

(It seems that it works ok to pass regular files (not directories) to
"find", but I'm not sure if it's portable.)

Attachment Content-Type Size
0001-Allow-passing-files-on-command-line-of-pgperltidy.patch text/plain 2.5 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2023-05-25 09:13:06 pg_walinspect last query typo
Previous Message Stavros Koureas 2023-05-25 09:10:06 Logical Replication Conflict Resolution