Tag ps1
has no guidance, with only 44 questions using it, however the main problem is .ps1
is a PowerShell profile and script extension, but is being used both for PowerShell and other shells that really aren't relevant to it:
- While BSD/Linux shells do use the
PS1
variable within their shell RC files, it's so widely attributed with PowerShell even syntax highlighter highlight.js usesps1
for PowerShell (which will be a supported code syntax on this site when it's eventually added and that oversight bug fixed)
If the ps1
tag should be used, it would make far more sense for BSD/Linux shell PS1
variable questions to be tagged with their shell and shell config tags, not tag ps1
, and for this guidance to be within the tag's guidance.
ps-1
since that would also apply to PS/1 hardware like legacy keyboard/mice)..ps1
is a widely used file extension on billions of files and billions of machines since every Windows install comes with more than one.ps1
file, and would seem to make more sense to treat it as a file extension likebatch-file
,sh
, etc. (if notps1
, perhapsps1-file
?)powershell
tag is enough,PS1
variable is much more specific and better fit - but don't thinkbash-ps1
is accurate as it applies to lots of shells.