Talk:Readline interface: Difference between revisions

Line 9:

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?).-- [[User:Gerard Schildberger|Gerard Schildberger]] 17:12, 1 June 2012 (UTC)

:i don't get what you mean. what exactly is the issue with the up arrow? it works fine in about any shell or readline interface i know.--[[User:EMBee|eMBee]] 13:30, 18 June 2012 (UTC)

:: I have no issue with the UP arrow. I never said or implied that I did. If you can define what half of the function keys that make up the command history :"support structure", I'd be amazed. I stated that it's a complicated set of commands, of which almost everybody only used the UP arrow key, and hardly anybody even bothers to configure it (at least, that's my experience when observing other people's computers). I also never implied that it doesn't work fine. I said it was complicated and hard to remember which function key does what. It still is surprising when you look at the properties of the "prompt" window, that the UP arrow is never mentioned, just the command history, buffer size, # of buffers (what the heck is a buffer, why not call it a command or some such?), and a check-box for discarding duplicates (duplicate commands that are sequential, or entered at anytime?). This is in reference to Windows. -- [[User:Gerard Schildberger|Gerard Schildberger]] 20:23, 19 June 2012 (UTC)

I was going to add such functionality to the REXX example, but the code would've been far from simple.