Talk:Readline interface: Difference between revisions

→‎What is meant by "history"?: added another section. -- ~~~~
(→‎What is meant by "history"?: You didn't know? Wow…)
(→‎What is meant by "history"?: added another section. -- ~~~~)
Line 3:
Is history simply not removing what is in the console when a new command is run? --[[User:Crazyfirex|Crazyfirex]] 21:26, 8 December 2011 (UTC)
: No. History is pressing the up arrow to retrieve a previously-typed command (one of a sequence of them in fact) that you can then run again, or edit before submitting. It ''greatly'' improves the productivity and usability of a command-line interface. –[[User:Dkf|Donal Fellows]] 03:26, 9 December 2011 (UTC)
 
==a simple program ...==
I think anyone attempting this task will soon find that's it not simple to provide a "history" suitable for re-doing commands. Witness Microsoft's DOS with its ''up arrow'' (retrieve/re-do) function along with all the F1 --> F12 functions, the latter being too complicated to use and hard to remember which function key does what (I still ponder, what where those coders thinking?). I was going to add such functionality to the REXX example, but the code would've been far from simple. So I elected to just have the option for the user to list the history of all commands entered, and let the user pick which one (by number), or just choose the last command to re-execute. I couldn't added more support to just limit the last ''n'' entries (for the command history), and/or let the user choose how many commands to list. But again, that would've added more complexity to an already burgeoning program, and the goal of the task was to implement a '''simple''' (ha!, good luck with that!) program, and in that, I fear, I may have failed. I hope I showed how to add commands, handle aliases, and full abbreviations (modeled after IBM VM/CMS version of what abbreviations are). Of course, one man's simple program is another's monstrosity. -- [[User:Gerard Schildberger|Gerard Schildberger]] 17:12, 1 June 2012 (UTC)