pgindent vs. pgperltidy command-line arguments
От
Peter Eisentraut
Тема
pgindent vs. pgperltidy command-line arguments
Дата
Msg-id
45aacd8a-5265-d9da-8df2-b8e2c0cf6a07@eisentraut.org
Список
Дерево обсуждения
pgindent vs. pgperltidy command-line arguments Peter Eisentraut <peter@eisentraut.org>
Re: pgindent vs. pgperltidy command-line arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: pgindent vs. pgperltidy command-line arguments Peter Eisentraut <peter@eisentraut.org>
Re: pgindent vs. pgperltidy command-line arguments Andrew Dunstan <andrew@dunslane.net>
Re: pgindent vs. pgperltidy command-line arguments Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
Re: pgindent vs. pgperltidy command-line arguments Peter Eisentraut <peter@eisentraut.org>
Re: pgindent vs. pgperltidy command-line arguments Andrew Dunstan <andrew@dunslane.net>
Re: pgindent vs. pgperltidy command-line arguments Peter Eisentraut <peter@eisentraut.org>
Re: pgindent vs. pgperltidy command-line arguments Andrew Dunstan <andrew@dunslane.net>
Re: pgindent vs. pgperltidy command-line arguments Daniel Gustafsson <daniel@yesql.se>
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.)
В списке pgsql-hackers по дате отправления
