Category talk:UNIX Shell

Implementation

Additions to the "implementation" section too long? Separate into a separate page somewhere?

I have mixed feelings about the section I just added to this section. On the one hand I know (from years of scripting, and supporting other shell scripters and occasionally teaching classes in the topic) that this information is important. On the other hand it seem like it should go into its own page somewhere.

On another tentacle, I'm not sure how much this relates to the core focus of this site. The details of how various Bourne-compatible shells handle their subshells, pipelines and variables have little or no analogue in other programming languages.

Thoughts?

JimD 12:17, 12 October 2007 (MDT)

I think this is really meaty information that would be wonderful to have on this site, but I agree that it is too much for this page. I think we strive for just a couple paragraph summary on each language category page, so that you don't have to scroll down to see the tasks solved. How about making a new page and link to it from here? Can't think of a good name for it off the top of my head. --IanOsgood 19:44, 12 October 2007 (MDT)

<lang bash> versus <lang sh>

I use <lang bash> for all Bourne-compatible examples, including pdksh and plain Bourne Shell code. Some other contributors use <lang sh>. Which is better, <lang bash> or <lang sh>? I prefer <lang bash>, because the page at Rosetta Code:Village Pump/Syntax Highlighting says to use "bash" for "UNIX Shell". --Kernigh 16:09, 22 August 2011 (UTC)

When it works with Bourne Shell

• Do not make a long list of Bourne-compatible shells above each Bourne-compatible solution. A single {{works with|Bourne Shell}} is enough. Do not add works with Almquist Shell, works with Korn Shell, works with Bash, ...
• Do not post two copies of the same script. There should not be an extra copy that only has #!/bin/bash instead of #!/bin/sh, only because the script also works with Bash.

--Kernigh 02:42, 30 August 2011 (UTC)