[Idle-dev] CVS: idle extend.txt,1.2,1.3

[Kurt B. Kaiser]

Update of /cvsroot/idlefork/idle
In directory usw-pr-cvs1:/tmp/cvs-serv7385

Modified Files:
	extend.txt 
Log Message:
py-cvs-2001_07_13 (Rev 1.4) merge

"Quick update to the extension mechanism (extend.py is gone, long live
config.txt)" --GvR


Index: extend.txt
===================================================================
RCS file: /cvsroot/idlefork/idle/extend.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** extend.txt	2001/07/04 03:15:10	1.2
--- extend.txt	2001/07/14 05:18:59	1.3
***************
*** 8,12 ****
  
  The list of extensions loaded at startup time is configured by editing
! the file extend.py; see below for details.
  
  An IDLE extension is defined by a class.  Methods of the class define
--- 8,12 ----
  
  The list of extensions loaded at startup time is configured by editing
! the file config.txt; see below for details.
  
  An IDLE extension is defined by a class.  Methods of the class define
***************
*** 87,95 ****
          "...Do what you want here..."
  
! The final piece of the puzzle is the file "extend.py", which contains a
! simple table used to configure the loading of extensions.  This file
! currently contains a single list variable named "standard", which is a
! list of extension names that are to be loaded.  (In the future, other
! configuration variables may be added to this module.)
  
  Extensions can define key bindings and menu entries that reference
--- 87,109 ----
          "...Do what you want here..."
  
! The final piece of the puzzle is the file "config.txt", which is used
! to to configure the loading of extensions.  For each extension,
! you must include a section in config.txt (or in any of the other
! configuration files that are consulted at startup: config-unix.txt,
! config-win.txt, or ~/.idle).  A section is headed by the module name
! in square brackets, e.g.
! 
!     [ZoomHeight]
! 
! The section may be empty, or it may define configuration options for
! the extension.  (See ParenMatch.py for an example.)  A special option
! is 'enable': including
! 
!     enable = 0
! 
! in a section disables that extension.  More than one configuration
! file may specify options for the same extension, so a user may disable
! an extension that is loaded by default, or enable an extension that is
! disabled by default.
  
  Extensions can define key bindings and menu entries that reference