On Mon, 21 Jul 2014 17:57:22 +0200, Lele Gaifax wrote: > Chris Angelico <ros...@gmail.com> writes: > >> Take, for instance, the behaviour of Windows's cmd.exe editing keys: >> enter three commands, then up-arrow three times and hit enter, then >> press down, enter, down, enter. You'll repeat the three commands. In >> other interfaces (eg GNU readline), you'd do the same job by pressing >> up, up, up, enter each time. Personally, I find the cmd.exe behaviour >> extremely surprising, especially when I've been working with some very >> similar commands (imagine: ./configure some_bunch_of_args; make; >> some_command_to_test; rm -rf *; git checkout HEAD - then repeat with a >> different set of configure arguments), and I end up "stuck half way up >> command history", wondering why I'm not seeing what I wanted. Can be >> extremely awkward. But even so, I don't call this a bug. > > Granted, the readline library exposes a "operate-and-get-next" function, > by default bound to \C-o, with the same behaviour as the cmd.exe one. I > find it very handy in the scenario you picted. So again, "feature" and > "bug" may be effectively subjective :-)
Have you actually got that working in Python with the readline module? I've tried and tried and cannot get it to work. Any hints gratefully appreciated. -- Steven -- https://mail.python.org/mailman/listinfo/python-list
