|
On Saturday 13 October 2001 11:04 pm, I wrote (but forgetting the footnote): [snip] ...It's easy > enough (on Linux at least) to get help *before* running the command, > but not once you start typing it. I usually search back through command > history[1] to pull back a command that did what I wanted, rather than > try to figure out all the options again. [1] This is one I which I had on OS/400. history | grep mycmd to see all the times I used a particular command. There was a HISTORY command written in '97 from MC (?) that can pull out commands for a job, but it's limited to the selected job. F9 retrieval is okay, but very limited (no search, and only backwards scrolling - miss the one you want; start again :-( ). The *nix history logs the last n commandline requests (in my case n=1000) making this sort of search easy. I guess it's similar to an SQL session log, but as it's already in a file, it's more easy to process. Regards, Martin -- martin@dbg400.net / jamaro@firstlinux.net http://www.dbg400.net DBG/400 - DataBase Generation utilities Open Source test environment tools for the AS/400 / iSeries and miscellaneous database & spooled file management commands.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.