[issue43654] IDLE: Fix tab completion after settings and some keys

2022-01-20 Thread Tal Einat
Tal Einat added the comment: Terry, for all intents and purposes you're the one in charge of IDLE now. I suggest deciding whether to change all three bindings as in the current PR or only the one for completions. Just le me know and if needed I'll make a new PR. -- _

[issue43654] IDLE: Fix tab completion after settings and some keys

2021-06-06 Thread Tal Einat
Tal Einat added the comment: > The unknown is whether anyone has changed these pseudoevent bindings and if > so, how much do we care? Let's ask on idle-dev. > Guido, do you have any comment on this proposal from a change policy > perspective? I'm not an ex-BDFL, but I can't think of a reas

[issue43654] IDLE: Fix tab completion after settings and some keys

2021-06-03 Thread Raymond Hettinger
Raymond Hettinger added the comment: > The unknown is whether anyone has changed these > pseudoevent bindings and if so, how much do we care? I don't think we care. Getting tab completion sorted out is the priority. -- nosy: +rhettinger ___ Pyth

[issue43654] IDLE: Fix tab completion after settings and some keys

2021-06-01 Thread Terry J. Reedy
Terry J. Reedy added the comment: Currently, the keys that define certain pseudoevents and invoke the associated event handlers are fixed: tab, '.', and within strings, '/' and '\' for completions, '(' and ')' for calltip open and close, and ')', ']', and '}' for opener matching. Note that