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
BASH shell history list | 265 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
BASH shell history list
Authored by: Ian Al on Saturday, April 13 2013 @ 03:51 AM EDT
I think all Unix shells provide a much simpler implementation which 'allows
“[t]he user [to] input[] data for a field of [a] form by selecting an item from
the displayed historical list which corresponds to the particular field.”'

Using the 'Up' and 'Down' arrows, the historical list of entries previously
entered into the command line field can be browsed and entered into the field.

The patent does not seem to exclude forms that have only one field, such as a
command line. My Amiga has the same feature. I still have it if they want one to
demonstrate prior art in court, again.

---
Regards
Ian Al
Software Patents: It's the disclosed functions in the patent, stupid!

[ Reply to This | Parent | # ]

Whoa...
Authored by: Anonymous on Saturday, April 13 2013 @ 09:13 AM EDT
Just tested that...

Thank you, thank you and thank you again!

For as long as I've used history, it has ALWAYS been in the form of:

$ history | grep $whatIRemember

And as my memory leaks become more frequent with age, I have wondered more and
more why history hasn't been made easier to deal with.

Bah! I'm almost afraid to ask how long thats been there.

[ Reply to This | Parent | # ]

BASH shell history list
Authored by: joef on Saturday, April 13 2013 @ 11:46 AM EDT
And you can 'set -o vi' or 'set -o emacs' (as you prefer) in ~/.bashrc and use
the editing features on the history list. This includes modifying a prior
command line to correct mis-types, change option settings, or change target
arguments. Or you can invoke the feature at any time, even if it's not in
.bashrc, by typing the command 'set -o <favorite editor>'.

[ 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 )