Re: run pgindent on a regular basis / scripted manner

On 2023-02-13 Mo 09:02, Jelte Fennema wrote:
> On Sun, 12 Feb 2023 at 15:16, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>> I'm not sure how much more I really want to do here. Given the way pgindent now processes command line arguments, maybe the best thing is for people to use that. Use of git aliases can help. Something like these for example
>>
>>
>> [alias]
>>
>> dirty = diff --name-only --diff-filter=ACMU -- .
>> staged = diff --name-only --cached --diff-filter=ACMU -- .
>> dstaged = diff --name-only --diff-filter=ACMU HEAD -- .
>>
>>
>> and then you could do
>>
>> pgindent `git dirty`
>>
>>
>> The only danger would be if there were no dirty files. Maybe we need a switch to inhibit using the current directory if there are no command line files.
>>
>>
>> Thoughts?
> I think indenting staged or dirty files is probably the most common
> operation that people want to do with pgindent. So I think that having
> dedicated flags makes sense. I agree that it's not strictly necessary
> and git aliases help a lot. But the git aliases require you to set
> them up. To me making the most common operation as easy as possible to
> do, seems worth the few extra lines to pgindent.

OK, but I'd like to hear from more people about what they want.
Experience tells me that making assumptions about how people work is not
a good idea. I doubt anyone's work pattern is like mine. I don't want to
implement an option that three people are going to use.

>
> Sidenote: You mentioned untracked files in another email. I think that
> the --dirty flag should probably also include untracked files. A
> command to do so is: git ls-files --others --exclude-standard

Thanks for the info.

cheers

andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com