This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients cheryl.sabella, terry.reedy
Date 2018-12-28.04:17:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1545970663.03.0.706375304332.issue28097@roundup.psfhosted.org>
In-reply-to
Content
Response to history issues raised in PR:
1. Not erasing output/history is a feature: some shells save and restore recent history when close and open.  Shell restart is an alternative to that.  I fairly often replay statements after restart.
2. I think turning off cycling is feature bloat.  (I never do so for search.)
3. The one history feature that multiple people have asked for, on another issue, is retrieval with up/down arrow, as seems to be standard.  I now agree.

For items going under edit, which is already 'full', submenus will be needed.  Since history is Shell only, separate entries are ok, at least for now, instead of 'History' and a submenu with 'previous' and 'next'.
History
Date User Action Args
2018-12-28 04:17:45terry.reedysetrecipients: + terry.reedy, cheryl.sabella
2018-12-28 04:17:43terry.reedysetmessageid: <1545970663.03.0.706375304332.issue28097@roundup.psfhosted.org>
2018-12-28 04:17:43terry.reedylinkissue28097 messages
2018-12-28 04:17:42terry.reedycreate