Adding new docs for configuration/extensions/plugins.

docs/source/config/extensions.txt

@@ -0,0 +1,61 b''
+.. _extensions_overview:
+
+==================
+IPython extensions
+==================
+
+Configuration files are just the first level of customization that IPython
+supports. The next level is that of extensions. An IPython extension is an
+importable Python module that has a a few special function. By defining these
+functions, users can customize IPython by accessing the actual runtime objects
+of IPython.  Here is a sample extension::
+
+    # myextension.py
+
+    def load_ipython_extension(ipython):
+        # The ``ipython`` argument is the currently active 
+        # :class:`InteractiveShell` instance that can be used in any way.
+        # This allows you do to things like register new magics, plugins or
+        # aliases.
+
+    def unload_ipython_extension(ipython):
+        # If you want your extension to be unloadable, put that logic here.
+
+This :func:`load_ipython_extension` function is called after your extension is
+imported and the currently active :class:`InteractiveShell` instance is passed
+as the only argument. You can do anything you want with IPython at that point.
+
+The :func:`load_ipython_extension` will be called again is you load or reload
+the extension again. It is up to the extension author to add code to manage
+that.
+
+You can put your extension modules anywhere you want, as long as they can be
+imported by Python's standard import mechanism. However, to make it easy to
+write extensions, you can also put your extensions in
+``os.path.join(self.ipython_dir, 'extensions')``. This directory is added to
+``sys.path`` automatically.
+
+Using extensions
+================
+
+There are two ways you can tell IPython to use your extension:
+
+1. Listing it in a configuration file.
+2. Using the ``%load_ext`` magic function.
+
+To load an extension called :file:`myextension.py` add the following logic
+to your configuration file::
+
+    c.Global.extensions = [
+        'myextension'
+    ]
+
+To load that same extension at runtime, use the ``%load_ext`` magic::
+
+.. sourcecode:: ipython
+
+    In [1]: %load_ext myextension
+
+To summarize, in conjunction with configuration files and profiles, IPython
+extensions give you complete and flexible control over your IPython
+setup.

docs/source/config/plugins.txt

@@ -0,0 +1,23 b''
+.. _plugins_overview:
+
+===============
+IPython plugins
+===============
+
+IPython has a plugin mechanism that allows users to create new and custom
+runtime components for IPython. Plugins are different from extensions:
+
+* Extensions are used to load plugins.
+* Extensions are a more advanced configuration system that gives you access
+  to the running IPython instance.
+* Plugins add entirely new capabilities to IPython.
+* Plugins are traited and configurable.
+
+At this point, our plugin system is brand new and the documentation is 
+minimal. If you are interested in creating a new plugin, see the following
+files:
+
+* :file:`IPython/extensions/parallemagic.py`
+* :file:`IPython/extensions/pretty.`
+
+As well as our documentation on the configuration system and extensions.

docs/source/config/index.txt

@@ -1,13 +1,15 b''
 .. _config_index:
 
 ===============================
 Configuration and customization
 ===============================
 
 .. toctree::
    :maxdepth: 2
 
    overview.txt
+   extensions.txt
+   plugins.txt
    ipython.txt
    editors.txt
    old.txt

docs/source/config/ipython.txt

@@ -1,136 +1,136 b''
 .. _configuring_ipython:
 
 ===========================================================
 Configuring the :command:`ipython` command line application
 ===========================================================
 
 This section contains information about how to configure the
 :command:`ipython` command line application. See the :ref:`configuration
 overview <config_overview>` for a more general description of the
 configuration system and configuration file format.
 
 The default configuration file for the :command:`ipython` command line application
 is :file:`ipython_config.py`.  By setting the attributes in this file, you
 can configure the application.   A sample is provided in
 :mod:`IPython.config.default.ipython_config`.  Simply copy this file to your
 IPython directory to start using it.
 
 Most configuration attributes that this file accepts are associated with
 classes that are subclasses of :class:`~IPython.core.component.Component`.
 
 A few configuration attributes are not associated with a particular 
 :class:`~IPython.core.component.Component` subclass.  These are application
 wide configuration attributes and are stored in the ``Global`` 
 sub-configuration section.  We begin with a description of these 
 attributes.
 
 Global configuration
 ====================
 
 Assuming that your configuration file has the following at the top::
 
     c = get_config()
 
 the following attributes can be set in the ``Global`` section.
 
 :attr:`c.Global.display_banner`
     A boolean that determined if the banner is printer when :command:`ipython`
     is started.
 
 :attr:`c.Global.classic`
     A boolean that determines if IPython starts in "classic" mode.  In this
     mode, the prompts and everything mimic that of the normal :command:`python`
     shell
 
 :attr:`c.Global.nosep`
     A boolean that determines if there should be no blank lines between
     prompts.
 
 :attr:`c.Global.log_level`
     An integer that sets the detail of the logging level during the startup
     of :command:`ipython`.  The default is 30 and the possible values are
     (0, 10, 20, 30, 40, 50).  Higher is quieter and lower is more verbose.
 
 :attr:`c.Global.extensions`
     A list of strings, each of which is an importable IPython extension. An
     IPython extension is a regular Python module or package that has a
     :func:`load_ipython_extension(ip)` method. This method gets called when
     the extension is loaded with the currently running
     :class:`~IPython.core.iplib.InteractiveShell` as its only argument. You
     can put your extensions anywhere they can be imported but we add the
     :file:`extensions` subdirectory of the ipython directory to ``sys.path``
     during extension loading, so you can put them there as well. Extensions
     are not executed in the user's interactive namespace and they must be pure
     Python code. Extensions are the recommended way of customizing
     :command:`ipython`. Extensions can provide an
     :func:`unload_ipython_extension` that will be called when the extension is
     unloaded.
 
 :attr:`c.Global.exec_lines`
     A list of strings, each of which is Python code that is run in the user's
     namespace after IPython start. These lines can contain full IPython syntax
     with magics, etc.
 
 :attr:`c.Global.exec_files`
     A list of strings, each of which is the full pathname of a ``.py`` or
     ``.ipy`` file that will be executed as IPython starts. These files are run
     in IPython in the user's namespace. Files with a ``.py`` extension need to
     be pure Python. Files with a ``.ipy`` extension can have custom IPython
     syntax (magics, etc.). These files need to be in the cwd, the ipythondir
     or be absolute paths.
 
 Classes that can be configured
 ==============================
 
 The following classes can also be configured in the configuration file for
 :command:`ipython`:
 
 * :class:`~IPython.core.iplib.InteractiveShell`
 
 * :class:`~IPython.core.prefilter.PrefilterManager`
 
 * :class:`~IPython.core.alias.AliasManager`
 
 To see which attributes of these classes are configurable, please see the
 source code for these classes, the class docstrings or the sample
 configuration file :mod:`IPython.config.default.ipython_config`.
 
 Example
 =======
 
 For those who want to get a quick start, here is a sample
 :file:`ipython_config.py` that sets some of the common configuration
 attributes::
 
     # sample ipython_config.py
     c = get_config()
 
     c.Global.display_banner = True
     c.Global.log_level = 20
     c.Global.extensions = [
         'myextension'
     ]
     c.Global.exec_lines = [
         'import numpy',
         'import scipy'
     ]
     c.Global.exec_files = [
         'mycode.py',
         'fancy.ipy'
     ]
     c.InteractiveShell.autoindent = True
     c.InteractiveShell.colors = 'LightBG'
     c.InteractiveShell.confirm_exit = False
     c.InteractiveShell.deep_reload = True
     c.InteractiveShell.editor = 'nano'
     c.InteractiveShell.prompt_in1 = 'In [\#]: '
     c.InteractiveShell.prompt_in2 = '   .\D.: '
     c.InteractiveShell.prompt_out = 'Out[\#]: '
     c.InteractiveShell.prompts_pad_left = True
     c.InteractiveShell.xmode = 'Context'
 
     c.PrefilterManager.multi_line_specials = True
 
     c.AliasManager.user_aliases = [
      ('la', 'ls -al')
-    ]
  No newline at end of file
+    ]