Support ".ps1" PowerShell file type about ack3

[petdance]

Please point to the docs for it. Are there other extensions that might need to go with it? Are there any potential collisions with other files called .ps1 we should know about?

[thgossler]

PowerShell uses only the following defined extensions:

.ps1 => scripts (https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_scripts?view=powershell-7.2)

.psm1 => modules (https://learn.microsoft.com/en-us/powershell/scripting/developer/module/understanding-a-windows-powershell-module?view=powershell-7.2)

.psd1 => module manifest (https://learn.microsoft.com/en-us/powershell/scripting/developer/module/understanding-a-windows-powershell-module?view=powershell-7.2#module-manifests)

These extensions have no dependencies to other file types and should be unique as well.

[petdance]

So if you were to do ack foo --powershell, which of those files would you expect it to search? .ps1 only? .ps1 and .psm1?

Either way, make yourself an .ackrc file in your home directory, if you don't have one already, and add one of these two lines:

--type-add=powershell:ext:ps1

or

--type-add=powershell:ext:ps1,psm1

Then you'll have --powershell support. Ue it for a while and see how it works out.

We need someone to try it out before we make it official in ack itself.

[thgossler]

Thanks! Yes, I found the option to extend the config myself via .ackrc file or command line. This is great.

Still, it would be nice to have it supported out of the box.

Actually, I would expect .ps1 and .psm1 files to be searched (both contain relevant PS code), but not .psd1.

[petdance]

So have you been using the config aliases for a while? How long? With both ps1 and psm1 and not psd1?

it would be nice to have it supported out of the box.

Understood. I'm basically asking you to be a beta tester for this change. Maybe you'll turn up some sort of problem.

[petdance]

Done at f18e96a