Talk:KornShell

message: :>>>Ksh aim to respect the Shell Language Standard (POSIX 1003.2 "Shell and Utilities Language Committee").<<<
This sentence makes no sense. Shouldn't this be something like:
:"Ksh's aim is to replace the Shell Language ..."
I am just commenting on the wording. I don't know the specifics of KSH's goals.
:I think think wording in the article is correct. They want to be compatible with the standard POSIX shell, not replace it. --Merphant 05:51, 18 Nov 2003 (UTC)
thread_title:  Standards compliance 

message: "(as of 2005 only Solaris ships ksh88, all other Unix vendors migrated to ksh93 and even Linux distributions started shipping ksh93)"
is not entirely accurate: IBM still ships AIX with a modified ksh88 as /bin/ksh but has started shipping /bin/ksh93 for the same (starting at least @ version 5.2).
--Sonicbphuct 21:11, 12 December 2005 (UTC)
thread_title:  Vendors shipping ksh93 

message: The book cover is amusing (being signed by the band), but it's not terribly helpful here. Can anyone think of a reason that an article on the Korn shell NEEDS more than just an image of the logo? -Harmil 15:47, 20 March 2006 (UTC)
replies: text: I concur.  If I don't see any objections (other than it's humourous) here in the next couple of days I will remove it. Gh5046 20:25, 5 December 2006 (UTC)
thread_title:  Book cover 

message: Maybe it should be mentioned as well. 84.191.226.162 (talk) 02:17, 20 March 2008 (UTC)
replies: text: Sure, go for it.  Gh5046 (talk) 02:51, 20 March 2008 (UTC)
replies: text: I corrected the license terms. mksh, according to mirbsd.org, does not appear to use MirOS's own license, but rather the Modified BSD License and the ISC License. --Evice (talk) 07:26, 28 July 2014 (UTC)
thread_title:  what about [http://www.mirbsd.org/mksh.htm mksh]? 

message: Why did you remove the external link to the most widely refererenced korn shell script repository on the internet?  —Preceding unsigned comment added by 12.171.225.24 (talk) 21:33, 21 January 2009 (UTC)
replies: text: To those still interested in the answer: because such a link is irrelevant. A clever mind can easily get why and wouldn′t ask the question in the first place. Others, you will content yourselves with the following hint: we don′t put links to software repositories in the “Software” article, we don′t put links to Git/SVN repositories in the “Source code” article, and so on. I hope you manage to grasp the recurring idea in all these instances. 213.131.238.28 (talk) 14:29, 16 March 2012 (UTC)
thread_title:  why did you remove... 

message: The name of a product is exactly how the manufacturer of that product spells it, up to the smallest quirk like a space or capital. The name of the product in question, i.e. ksh and ksh93 standard UNIX programs, is KornShell. We should rename the article likewise. The current name of this article (“Korn shell”) is mangled: putting a space between “Korn” and “Shell” and de-capitalizing the latter is someone′s unjustified gag. I will create an account and rename the article myself. 213.131.238.28 (talk) 14:44, 16 March 2012 (UTC)
replies: text: It's not unjustified.  From WP:COMMONNAME, "Wikipedia does not necessarily use the subject's "official" name as an article title; it prefers to use the name that is most frequently used to refer to the subject in English-language reliable sources."  Bolsky and Korn referred to it as the "KornShell" in "The KornShell Command and Programming Language" (1989).  But Kochan and Wood called it the "Korn shell" in "UNIX Shell Programming" (1985), as did Rosenblatt in "Learning the Korn Shell" (1993).  "Korn shell" is also far more common on web, with about 751,000 results for "Korn shell" compared to just 399,000 for "KornShell".  Similarly, searches at Amazon.com for "Korn shell" turn up 56 results compared to just 20 for KornShell.  I think the change to "KornShell" should be reverted.  Msnicki (talk) 03:25, 18 March 2012 (UTC)
replies: text: This sounds like a similar case of UNIX vs. Unix, because mksh is officially the MirBSD Korn Shell, with a space. --Evice (talk) 07:30, 28 July 2014 (UTC)
thread_title:  The name must be changed 

message: What should it be, Korn shell or KornShell? The article uses both. --Mortense (talk) 23:45, 23 March 2016 (UTC)
thread_title:  Korn shell or KornShell? 

message: In the Design section, the article states that
thus giving the impression that the KornShell was written to be POSIX-compliant, which is misleading as it was actually written way earlier than the standard and that
Tinm (talk) 19:05, 4 May 2016 (UTC)
thread_title:  KornShell & POSIX, wording 

message: Given this:
 ksh93v-64  --version
  version         sh (AT&T Research) 93v- 2014-12-24
and the fact that there is close to no activity since David started to work for Google, I tend call ksh93v- very stable. Schily (talk) 13:11, 17 January 2017 (UTC)
replies: text: Has it anything official? Debian/sid still has 93u. Vincent Lefèvre (talk) 15:01, 17 January 2017 (UTC)
replies: text: It is the latest version that could be loaded from the AT&T server before it stopped working. I could not find it in the GITlab repo, but someone told me that it is contained in a branch that needs to be specified explicitly. Schily (talk) 16:08, 17 January 2017 (UTC)
thread_title:  ksh93v 

message: Hello fellow Wikipedians,
I have just modified 2 external links on KornShell. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://www.webcitation.org/61A4Ay7bL?url=http://www.cs.mun.ca/~michael/pdksh/LEGAL to http://www.cs.mun.ca/~michael/pdksh/LEGAL
*Added archive https://web.archive.org/web/20040216045828/http://web.cs.mun.ca/~michael/pdksh/ to http://web.cs.mun.ca/~michael/pdksh/
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 10:59, 12 December 2017 (UTC)
thread_title:  External links modified