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 marco, roger.serwy, terry.reedy
Date 2011-12-18.03:01:49
SpamBayes Score 2.9709604e-06
Marked as misclassified No
Message-id <1324177311.64.0.633614644181.issue13586@psf.upfronthosting.co.za>
In-reply-to
Content
I am running 3.2.2 on 64-bit Win7Pro, which should not make a difference. So why did ^H work right for me yesterday and not for Marco today.

Retrying with fresh IDLEs I discovered the following: selections do not initially appear in the find part of a Replace box (^H). But after selecting and opening a Find box (^F) with something selected, the same text appears in Replace boxes regardless of the actual selection, even if there is no selection -- until another Find box is opened.

So I was fooled yesterday because I tried ^F first to see what the 'correct' behavior was and then did ^H with the same selection. And I did the same in both Shell and Edit windows. When testing, order matters ;-).

I discovered something else I am not sure is what we want. Clicking Find in a Replace box leaves the box open so one can Find again. Clicking Find in a Find box closes it. So you need ^F and Find to re-search.
History
Date User Action Args
2011-12-18 03:01:51terry.reedysetrecipients: + terry.reedy, roger.serwy, marco
2011-12-18 03:01:51terry.reedysetmessageid: <1324177311.64.0.633614644181.issue13586@psf.upfronthosting.co.za>
2011-12-18 03:01:51terry.reedylinkissue13586 messages
2011-12-18 03:01:50terry.reedycreate