decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
shell history history :) | 265 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
shell history history :)
Authored by: xtifr on Saturday, April 13 2013 @ 04:38 PM EDT
I'm pretty sure ksh predates readline. In fact, I think readline was created as
a generalization of the history features available in ksh (which was originally
AT&T code). Of course, ksh was inspired by features available in emacs...

The original bourne shell didn't have history. History was introduced with csh,
but csh used special characters to recall items from history, and if you wanted
to edit, you used a special command to invoke your editor on your history. Ksh
was the first shell to give us fully interactive history, and editor-like
command-line editing. It really was way ahead of its time. It even had the
option (as bash has) of selecting emacs mode or vi mode for editing.

Then there's tcsh, which added ksh-like/readline-like features to csh. It's
mostly (mercifully) forgotten, except amongst the most die-hard csh fans.
There's also zsh, which tried to combine the best features of csh and ksh, and
resulted in something completely incompatible with any sorts of standards, but
which still manages to retain a core fan base.

Then there's the POSIX shell, which, despite what you might expect, is not the
same as the original bourne shell. In fact, the POSIX shell is closer to ksh in
its set of required features.

---
Do not meddle in the affairs of Wizards, for it makes them soggy and hard to
light.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )