Skip to main content
Super User

Return to Question

Typo correction
Source Link
JW0914
JW0914
  • 8.6k
  • 9
  • 8

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 uses ps1 for PowerShell (which will be a supported code syntax on this site when it's eventually added and that oversight bug fixed)

If the psips1 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.

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 uses ps1 for PowerShell (which will be a supported code syntax on this site when it's eventually added and that oversight bug fixed)

If the psi 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.

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 uses ps1 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.

Source Link
JW0914
JW0914
  • 8.6k
  • 9
  • 8

Should the [ps1] tag be used, and if not, should it be removed?

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 uses ps1 for PowerShell (which will be a supported code syntax on this site when it's eventually added and that oversight bug fixed)

If the psi 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.