Author paulsfo
Recipients Al.Sweigart, littleq0903, ned.deily, paulsfo, roger.serwy, suddha.sourav, taleinat, terry.reedy
Date 2016-05-13.21:34:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1463175240.76.0.709979105056.issue15786@psf.upfronthosting.co.za>
In-reply-to
Content
hi Terry,  thanks for all the responses.

Well, what *I* found maddening was that typing  "os." pause "g" works but typing  "os.g" (with no pause) does nothing. :)  But, anyway, I guess you're saying that that's as designed.


>The list is not supposed to shrink. Having everything disappear on a typo would not seem good to me.

   Actually, I think that many widgets do work that way, but I think that, here, I agree with you, since the user might notice a nearby entry which is what they wanted.

What about my "b)" (copied just below)?  Is there a reason not to autocomplete what's on the command line, as is done if you *arrow* to a selection?  Again, not nearly as big an issue as the original hang but I can't think of a reason not to autocomplete in this case, and the code to do so must already exist. 

 b) say I want os.get_terminal_size.  I type "os." and wait for the popup to appear (see 'c)' for why this is necessary); then I type 'get_t".   Now  "get_terminal_size" is visible and selected but autocompletion doesn't occur.  I.E., I still have 'os.get_t" below the popup.  To get the full word I have to arrow *away* from the correct answer and then arrow back to it.  Now "get_terminal_size" appears below the popup.  This is obviously less serious, and less mysterious, than the original hang issue, but it's still a usability issue.
History
Date User Action Args
2016-05-13 21:34:00paulsfosetrecipients: + paulsfo, terry.reedy, taleinat, ned.deily, roger.serwy, Al.Sweigart, littleq0903, suddha.sourav
2016-05-13 21:34:00paulsfosetmessageid: <1463175240.76.0.709979105056.issue15786@psf.upfronthosting.co.za>
2016-05-13 21:34:00paulsfolinkissue15786 messages
2016-05-13 21:34:00paulsfocreate