There are these two - and . Moreover,

I'm wondering what's the point of having the two of these separate. If a script is not a shell script, then it's more about programming than Unix/Linux. Right?

I don't mind having a separate tag, but would like to clarify the usage.

  • 2
    I, too, have wondered this. Maybe scripting could cover python, awk, perl, and other languages that aren't typically login shells like ksh, zsh, bash, etc? – Jeff Schaller May 2 '17 at 15:21
  • 1
    @JeffSchaller They've not been used consistently. Similar questions are either /shell-script + /bash and /scripting + /bash. – Tomasz May 2 '17 at 15:51
  • 1
    Agreed, which is why I upvoted your Q and wondered about possible usage guidance. – Jeff Schaller May 2 '17 at 16:28
  • 1
    @JeffSchaller If I were to vote for a solution, I'd go for a merge under the /scripting or /script banner. Shell scripts need a specifying tag describing the interpreter. So do non-shell scripts. I'd add this directive to the tag's usage info. Otherwise they will be cross-misused both ways. – Tomasz May 2 '17 at 16:38
  • To me, scripting is the use of any interpreted programming language. While /shell-script definitely falls into that, it's actually more of a subset. Python and Ruby scripts are common in newer systems, and AWK is common in older systems. While some would say these are programming languages, so are the modern shells. – Peter Jan 11 '18 at 18:56

You must log in to answer this question.

Browse other questions tagged .