Re: What's wrong with Windows Command Prompt (was Re: Error Testing)

2013-10-21 Thread David Robinow
On Sat, Oct 19, 2013 at 4:35 PM, Terry Reedy tjre...@udel.edu wrote: On 10/19/2013 2:31 PM, Tim Chase wrote: On 2013-10-19 14:08, David Robinow wrote: On Sat, Oct 19, 2013 at 9:01 AM, Chris Angelico wrote: You can try all these out in the interactive interpreter (you probably have IDLE

Re: What's wrong with Windows Command Prompt (was Re: Error Testing)

2013-10-21 Thread Tim Chase
On 2013-10-21 15:55, David Robinow wrote: I wasn't aware that the interactive interpreter on Linux had features that the Windows version didn't. I'm curious what those features might be. It's mostly the benefits that come from being built with the readline library, meaning you get - command

What's wrong with Windows Command Prompt (was Re: Error Testing)

2013-10-19 Thread Terry Reedy
On 10/19/2013 2:31 PM, Tim Chase wrote: On 2013-10-19 14:08, David Robinow wrote: On Sat, Oct 19, 2013 at 9:01 AM, Chris Angelico wrote: You can try all these out in the interactive interpreter (you probably have IDLE installed, which on Windows is rather nicer to work with than the default

Re: What's wrong with Windows Command Prompt (was Re: Error Testing)

2013-10-19 Thread Chris Angelico
On Sun, Oct 20, 2013 at 7:35 AM, Terry Reedy tjre...@udel.edu wrote: Idle can recall previous input two different ways, by cursor or key. One can use the mouse to select where to edit. CP requires use of arrow keys to move the cursor around. Idle recall input *statements*. CP recalls input