Vedran Čačić added the comment:
Not only that, but when you're on the ground you have a much more diverse set
of options for moving. `s` is "enter a different tower", `r` is "exit a tower",
`n` is "move to the next tower", `j` is "teleport" and so on. :-)
Also for objects... you have "look
Terry J. Reedy added the comment:
Thank you for the tutorial example. Thinking of execution frames as stacked
rooms in a tower in a text adventure game is an interesting metaphor.
I duplicated the tests of idleConf.current_colors_and_keys with 'Theme' for
'Keys' and one failed until
Roundup Robot added the comment:
New changeset f198457d1475 by Terry Jan Reedy in branch 'default':
Issue #27821: Fix bug in idlelib.comfig function and add new tests.
https://hg.python.org/cpython/rev/f198457d1475
--
nosy: +python-dev
___
Python
Vedran Čačić added the comment:
Well, I don't know how good this comment box is for a pdb tutorial. :-) And I
learned it a long time ago, so I don't really remember how it is to not know
it. :-/ The main reason I love it is purely sentimental: it reminds me of those
silly text-based adventure
Terry J. Reedy added the comment:
Vedran, I have used IDLE's imperfect visual debugger and was thinking about how
I might use it to solve this problem. But I have never used pdb. Perhaps I
should learn it. Please explain how you used set_trace to track down this bug.
For #24265, I have
Terry J. Reedy added the comment:
Thanks for tracing further. That is the new bug in .0a3. "'Theme'" should be
"section", as in the next two GetOption calls. You should then not need a
custom theme. My new tests did not cover all the possible cases, so I should
add more along with the
Vedran Čačić added the comment:
But there is something _I_ can do now. :-)
I put a pdb.set_trace in that code you quoted, and went exploring. And here is
what I found.
It calls
currentOption = idleConf.CurrentKeys()
That one calls
return self.current_colors_and_keys('Keys')
and _that
Terry J. Reedy added the comment:
I can't make any sense of this report.
In configdialog.py, the DynOptionMenu self.optMenuKeysCuston is set in
LoadKeyConfig (line 1066) by
itemList = idleConf.GetSectionList('user', 'keys')
itemList.sort()
if not itemList:
Vedran Čačić added the comment:
P.S. I tested and no, IDLE Classic Windows (nor anything else except Veky2, I
deleted Veky) is not added to config-keys.cfg. My config-keys.cfg is
[Veky2]
toggle-auto-coloring =
tabify-region =
copy =
Vedran Čačić added the comment:
Neither. I see _two_ rows, lower one is as you quoted. So:
--Key Set
( ) Use a Built-in Key Set [IDLE Classic Windows --]
(*) Use a Custom Key Set [IDLE Classic Windows --]
Terry J. Reedy added the comment:
(Don't install .0a2, .0a1 is good enough as comparison.)
Are you saying that you see, in one line,
(*) Use a Custom Key Set [IDLE Classic Windows --]
(where -- is the select mini-button)
This would be wrong and would suggest that 'IDLE Classis Windows' was
Vedran Čačić added the comment:
Windows 10. No, I jumped from .0a1 to .0a3. Now I installed .0a4 and have the
same problem. I'm afraid of going back to .0a2, was taught long ago to never
downgrade anything. :-) But I have 3.5.1 installed separately, and its IDLE
keeps working without problem.
Terry J. Reedy added the comment:
I use a custom key set also and have no problem before or after the Modern Unux
patch (else I would not have applied it ;-). Did you have .0a2 installed?
Which Windows?
What I have in config-main.cfg is
[Keys]
default = False
name = Terry
[Theme]
New submission from Vedran Čačić:
I had a custom keymap in IDLE. Since I installed 3.6.0a3, it doesn't work
anymore. Worse, I cannot switch to anything except "IDLE Classic Windows" -
Apply does nothing, but when I click OK, it doesn't switch.
I suppose
14 matches
Mail list logo