Alan Moore added the comment:
Spent some time today with IDLE and PDB, and I've ruled out any other program
on my system as the culprit:
- I can create a tkinter GUI that will respond to a binding like
and it works fine.
- In pdb, I can bind <> to a callback and it is getting fired when
Ct
Alan Moore added the comment:
Ok, sorry to keep poking at this issue, but I think I was too hasty in blaming
firefox.
As I previously mentioned, IDLE "forgot" that Ctrl-N meant "next line" and
reverted it to "new window". I fixed that behavior by changing and resetting
the key set, HOWEVER
Alan Moore added the comment:
An interesting note this morning, and again I don't know if this is actually an
IDLE bug; I had left IDLE running overnight and opened a new code window this
morning. Somehow IDLE "forgot" that Ctrl-N means "next line" and not "new
window". I closed all my fir
Terry J. Reedy added the comment:
IDLE just tells tcl/tk via tkinter what function to call when particular UI
events happen. Recognizing UI events is handled between the OS window manager
and tcl/tk. So I am sure this is not an IDLE issue.
For another application to affect the Linux-tcl int
Alan Moore added the comment:
OK, it seems that closing all my firefox windows restored correct behavior to
IDLE. I can only guess that somehow firefox was eating the Ctrl-x.
Not sure if this is a firefox issue, a window manager issue, or an IDLE issue.
If you think it's not the latter, fe
New submission from Alan Moore :
Using IDLE 3.9.1 on Arch Linux.
In IDLE I've selected the "classic unix" key set. It worked for a while, then
stopped registering key combinations for more than one key (e.g. Ctrl-x Ctrl-s).
Have tried creating a custom key set and manually setting the shortc
