Logged In: YES 
user_id=679426

Hello,
  I think that showing / not showing the Code Context panel
should be a persistent setting - if the user wants it, it
will appear, and if he doesn't, it won't. The concept of "it
has an initial state, and you can change it afterwards if
you like" is confusing. Using a persistent setting makes a
keyboard shortcut unnecessary - I think that usually the
user will be happy with what he likes, and won't hide/show
the panel many times.
  So I made the <<toggle-code-context>> event save the new
setting in the user's configuration file. The new setting
will be applied also to new windows opened in the same
session. This required me to add a SetOption method to
configHandler.IdleConf. Also, the initialization of the
CodeContext instance required the menu item to be already
installed, but EditorWindow.load_extension installs the menu
items after it initializes the extension's instance. It
turns out that the menu items can be installed before the
instance initialization, so I changed it.
  Another problem was that the Code Context menu item was
installed on shell windows, but wasn't functioning, which
was quite confusing. So I added new optional configurations
for extensions: enable_shell and enable_editor, which allow
you to write extensions only for the editor/shell window,
without using the "isinstance(editwin, PyShell)" trick.
  About using a Text widget instead of a Label - it may
work, I don't know, but making the Label behave as I wanted
was hard enough, and it looks fine to me as it is, so I
leave it for now.

Bye Bye,
Noam