Jump to content

Talk:Readline interface: Difference between revisions

→‎a simple program ...: what makes up a readline interface with history? your contributions and opinions please!
(→‎a simple program ...: added a comment to a query. -- ~~~~)
(→‎a simple program ...: what makes up a readline interface with history? your contributions and opinions please!)
Line 10:
: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 plead guilty as charged :-)~~----
:: I also never implied that it doesn't work fine. I said it was complicated and hard to remember which function key does what.
::: you are right, i did actually miss that you wrote: "''the '''latter''' being too complicated''", sorry.
:::but you do say that providing a history that is suitable for redoing commands is not simple. and then you cite dos to substantiate that. if we assume that the up arrow key is suitable then why not just ignore the other stuff which most people don't use anyways. wouldn't that make it simpler? (now actually implementing the uparrow support is likely still not trivial but i'd consider it the simplest version that would actually feel like what i'd expect from a readline interface: working arrow keys.
:::however this task is still young, and i'd wait to see more opinions from others. as i said before, i expected this task to focus on existing realine implementations, anything beyond that, like your work, i consider a bonus, and i'd be happy to leave it as it is. thanks for the contribution.--[[User:EMBee|eMBee]] 03:32, 20 June 2012 (UTC)
:: 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.
Anonymous user
Cookies help us deliver our services. By using our services, you agree to our use of cookies.