On 2023-01-24 Tu 11:43, Tom Lane wrote: > Jelte Fennema <postg...@jeltef.nl> writes: >> Sounds like this conflict could be handled fairly easily by >> having a local git hook rerunning pgindent whenever >> you rebase a commit: >> 1. if you changed typedefs.list the hook would format all files >> 2. if you didn't it only formats the files that you changed > I think that would be undesirable, because then reindentation noise > in completely-unrelated files would get baked into feature commits, > complicating review and messing up "git blame" history. > The approach we currently have allows reindent effects to be > separated into ignorable labeled commits, which is a nice property. > >> Merge failures are one issue. But personally the main benefit that >> I would be getting is being able to run pgindent on the files >> I'm editing and get this weird +12 columns formatting correct >> without having to manually type it. Without pgindent also >> changing random parts of the files that someone else touched >> a few commits before me. > Yeah, that always annoys me too, but I've always considered that > it's my problem not something I can externalize onto other people. > The real bottom line here is that AFAICT, there are fewer committers > who care about indent cleanliness than committers who do not, so > I do not think that the former group get to impose strict rules > on the latter, much as I might wish otherwise. > > FWIW, Andrew's recent --show-diff feature for pgindent has > already improved my workflow for that. I can do > "pgindent --show-diff >fixindent.patch", manually remove any hunks > in fixindent.patch that don't pertain to the code I'm working on, > and apply what remains to fix up my new code. (I had been doing > something basically like this, but with more file-copying steps > to undo pgindent's edit-in-place behavior.) > >
I'm glad it's helpful. Here's another improvement I think will be useful when the new gadgets are used in a git hook: first, look for the excludes file under the current directory if we aren't setting $code_base (e.g if we have files given on the command line), and second apply the exclude patterns to the command line files as well as to files found using File::Find. I propose to apply this fairly soon. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
diff --git a/src/tools/pgindent/pgindent b/src/tools/pgindent/pgindent index 5eff1f8032..1f95a1a34e 100755 --- a/src/tools/pgindent/pgindent +++ b/src/tools/pgindent/pgindent @@ -63,6 +63,10 @@ $code_base ||= '.' unless @ARGV; $excludes ||= "$code_base/src/tools/pgindent/exclude_file_patterns" if $code_base && -f "$code_base/src/tools/pgindent/exclude_file_patterns"; +# also look under the current directory for the exclude patterns file +$excludes ||= "src/tools/pgindent/exclude_file_patterns" + if -f "src/tools/pgindent/exclude_file_patterns"; + # The typedef list that's mechanically extracted by the buildfarm may omit # some names we want to treat like typedefs, e.g. "bool" (which is a macro # according to <stdbool.h>), and may include some names we don't want @@ -421,8 +425,6 @@ File::Find::find( }, $code_base) if $code_base; -process_exclude(); - $filtered_typedefs_fh = load_typedefs(); check_indent(); @@ -430,6 +432,9 @@ check_indent(); # any non-option arguments are files to be processed push(@files, @ARGV); +# the exclude list applies to command line arguments as well as found files +process_exclude(); + foreach my $source_filename (@files) { # ignore anything that's not a .c or .h file