folio 0.2.0 → 0.3.0

data/CHANGES

@@ -1,2 +1,14 @@
+== 0.3.0 / 2008-09-17
 
+* 2 Major Enhancements
+
+    * Added XDG methods to Prompt class.  (#9a926a12a0b061c3ec9bfbd23f5387e65c1e7201)
+    * Renamed Prompt to Shell.  (#da2eb57bccd4400e0b272836ad9cf23ce23d6b19)
+
+
+== 0.2.0 / 2008-09-06
+
+* 1 Major Enhancements
+
+    * Started Repository.  (#20c00238d1401c2b4385f0a6109c2c001b922008)
 

data/MANIFEST

@@ -1,232 +1,16 @@
 doc
-doc/rdoc
-doc/rdoc/fr_file_index.html
-doc/rdoc/classes
-doc/rdoc/classes/Enumerator.html
-doc/rdoc/classes/Folio
-doc/rdoc/classes/Folio/FileObject.html
-doc/rdoc/classes/Folio/BlockDevice.html
-doc/rdoc/classes/Folio/Link.html
-doc/rdoc/classes/Folio/Document.html
-doc/rdoc/classes/Folio/CharacterDevice.html
-doc/rdoc/classes/Folio/Pipe.html
-doc/rdoc/classes/Folio/Device.html
-doc/rdoc/classes/Folio/Socket.html
-doc/rdoc/classes/Folio/Prompt.html
-doc/rdoc/classes/Folio/Directory.html
-doc/rdoc/classes/Folio/FileNotFound.html
-doc/rdoc/classes/Folio.html
-doc/rdoc/rdoc-style.css
-doc/rdoc/files
-doc/rdoc/files/README.html
-doc/rdoc/files/METADATA.html
-doc/rdoc/files/CHANGES.html
-doc/rdoc/files/lib
-doc/rdoc/files/lib/folio
-doc/rdoc/files/lib/folio/fileobject_rb.html
-doc/rdoc/files/lib/folio/link_rb.html
-doc/rdoc/files/lib/folio/document_rb.html
-doc/rdoc/files/lib/folio/errors_rb.html
-doc/rdoc/files/lib/folio/device_rb.html
-doc/rdoc/files/lib/folio/prompt_rb.html
-doc/rdoc/files/lib/folio/socket_rb.html
-doc/rdoc/files/lib/folio/pipe_rb.html
-doc/rdoc/files/lib/folio/directory_rb.html
-doc/rdoc/files/lib/folio_rb.html
-doc/rdoc/files/NEWS.html
-doc/rdoc/files/COPYING.html
-doc/rdoc/fr_class_index.html
-doc/rdoc/index.html
-doc/rdoc/created.rid
-doc/rdoc/fr_method_index.html
-doc/ri
-doc/ri/Folio
-doc/ri/Folio/Prompt
-doc/ri/Folio/Prompt/chmod-i.yaml
-doc/ri/Folio/Prompt/touch-i.yaml
-doc/ri/Folio/Prompt/%2b-i.yaml
-doc/ri/Folio/Prompt/glob-i.yaml
-doc/ri/Folio/Prompt/mkdir-i.yaml
-doc/ri/Folio/Prompt/ln-i.yaml
-doc/ri/Folio/Prompt/mv-i.yaml
-doc/ri/Folio/Prompt/files-i.yaml
-doc/ri/Folio/Prompt/entries-i.yaml
-doc/ri/Folio/Prompt/rm_rf-i.yaml
-doc/ri/Folio/Prompt/mkdir_p-i.yaml
-doc/ri/Folio/Prompt/documents-i.yaml
-doc/ri/Folio/Prompt/%2f-i.yaml
-doc/ri/Folio/Prompt/ln_sf-i.yaml
-doc/ri/Folio/Prompt/chown-i.yaml
-doc/ri/Folio/Prompt/ln_s-i.yaml
-doc/ri/Folio/Prompt/directories-i.yaml
-doc/ri/Folio/Prompt/directory_entries-i.yaml
-doc/ri/Folio/Prompt/cp-i.yaml
-doc/ri/Folio/Prompt/document_entries-i.yaml
-doc/ri/Folio/Prompt/rmdir-i.yaml
-doc/ri/Folio/Prompt/localize-i.yaml
-doc/ri/Folio/Prompt/chown_r-i.yaml
-doc/ri/Folio/Prompt/mode-i.yaml
-doc/ri/Folio/Prompt/cp_r-i.yaml
-doc/ri/Folio/Prompt/install-i.yaml
-doc/ri/Folio/Prompt/rm_r-i.yaml
-doc/ri/Folio/Prompt/cdesc-Prompt.yaml
-doc/ri/Folio/Prompt/chmod_r-i.yaml
-doc/ri/Folio/Prompt/file-i.yaml
-doc/ri/Folio/Prompt/%5b%5d-i.yaml
-doc/ri/Folio/Prompt/to_s-i.yaml
-doc/ri/Folio/Prompt/%5b%5d-c.yaml
-doc/ri/Folio/Prompt/new-c.yaml
-doc/ri/Folio/Prompt/fileutils-i.yaml
-doc/ri/Folio/Prompt/cd-i.yaml
-doc/ri/Folio/Prompt/rm-i.yaml
-doc/ri/Folio/Prompt/ls-i.yaml
-doc/ri/Folio/Link
-doc/ri/Folio/Link/lstat-i.yaml
-doc/ri/Folio/Link/link%3f-i.yaml
-doc/ri/Folio/Link/cdesc-Link.yaml
-doc/ri/Folio/Link/lchmod-i.yaml
-doc/ri/Folio/Link/lchown-i.yaml
-doc/ri/Folio/Link/symlink%3f-i.yaml
-doc/ri/Folio/Link/new-c.yaml
-doc/ri/Folio/Link/readlink-i.yaml
-doc/ri/Folio/Link/method_missing-i.yaml
-doc/ri/Folio/FileObject
-doc/ri/Folio/FileObject/chmod-i.yaml
-doc/ri/Folio/FileObject/split-i.yaml
-doc/ri/Folio/FileObject/unlink_force-i.yaml
-doc/ri/Folio/FileObject/rm_f-i.yaml
-doc/ri/Folio/FileObject/readable%3f-i.yaml
-doc/ri/Folio/FileObject/touch-i.yaml
-doc/ri/Folio/FileObject/symlink-i.yaml
-doc/ri/Folio/FileObject/writable_real%3f-i.yaml
-doc/ri/Folio/FileObject/delete_force-i.yaml
-doc/ri/Folio/FileObject/atime-i.yaml
-doc/ri/Folio/FileObject/ln-i.yaml
-doc/ri/Folio/FileObject/readable_real%3f-i.yaml
-doc/ri/Folio/FileObject/mv-i.yaml
-doc/ri/Folio/FileObject/size%3f-i.yaml
-doc/ri/Folio/FileObject/owned%3f-i.yaml
-doc/ri/Folio/FileObject/chardev%3f-i.yaml
-doc/ri/Folio/FileObject/link-i.yaml
-doc/ri/Folio/FileObject/grpowned%3f-i.yaml
-doc/ri/Folio/FileObject/stat%21-i.yaml
-doc/ri/Folio/FileObject/identical%3f-i.yaml
-doc/ri/Folio/FileObject/%3c%3d%3e-i.yaml
-doc/ri/Folio/FileObject/blockdev%3f-i.yaml
-doc/ri/Folio/FileObject/util-i.yaml
-doc/ri/Folio/FileObject/delete-i.yaml
-doc/ri/Folio/FileObject/relative-i.yaml
-doc/ri/Folio/FileObject/utime-i.yaml
-doc/ri/Folio/FileObject/fnmatch%3f-i.yaml
-doc/ri/Folio/FileObject/ln_sf-i.yaml
-doc/ri/Folio/FileObject/chown-i.yaml
-doc/ri/Folio/FileObject/restat-i.yaml
-doc/ri/Folio/FileObject/ln_s-i.yaml
-doc/ri/Folio/FileObject/inspect-i.yaml
-doc/ri/Folio/FileObject/size-i.yaml
-doc/ri/Folio/FileObject/exists%3f-i.yaml
-doc/ri/Folio/FileObject/cp-i.yaml
-doc/ri/Folio/FileObject/setgid%3f-i.yaml
-doc/ri/Folio/FileObject/symlink_force-i.yaml
-doc/ri/Folio/FileObject/socket%3f-i.yaml
-doc/ri/Folio/FileObject/unlink-i.yaml
-doc/ri/Folio/FileObject/%3d%3d-i.yaml
-doc/ri/Folio/FileObject/zero%3f-i.yaml
-doc/ri/Folio/FileObject/setuid%3f-i.yaml
-doc/ri/Folio/FileObject/exist%3f-i.yaml
-doc/ri/Folio/FileObject/basename-i.yaml
-doc/ri/Folio/FileObject/ctime-i.yaml
-doc/ri/Folio/FileObject/cdesc-FileObject.yaml
-doc/ri/Folio/FileObject/ln_f-i.yaml
-doc/ri/Folio/FileObject/directory%3f-i.yaml
-doc/ri/Folio/FileObject/document%3f-i.yaml
-doc/ri/Folio/FileObject/stat-i.yaml
-doc/ri/Folio/FileObject/install-i.yaml
-doc/ri/Folio/FileObject/to_s-i.yaml
-doc/ri/Folio/FileObject/extname-i.yaml
-doc/ri/Folio/FileObject/%5b%5d-c.yaml
-doc/ri/Folio/FileObject/writable%3f-i.yaml
-doc/ri/Folio/FileObject/link_force-i.yaml
-doc/ri/Folio/FileObject/mtime-i.yaml
-doc/ri/Folio/FileObject/new-c.yaml
-doc/ri/Folio/FileObject/pipe%3f-i.yaml
-doc/ri/Folio/FileObject/rename-i.yaml
-doc/ri/Folio/FileObject/sticky%3f-i.yaml
-doc/ri/Folio/FileObject/rm-i.yaml
-doc/ri/Folio/FileObject/dirname-i.yaml
-doc/ri/Folio/FileObject/fnmatch-i.yaml
-doc/ri/Folio/Pipe
-doc/ri/Folio/Pipe/cdesc-Pipe.yaml
-doc/ri/Folio/Pipe/new-c.yaml
-doc/ri/Folio/Pipe/pipe%3f-i.yaml
-doc/ri/Folio/Socket
-doc/ri/Folio/Socket/cdesc-Socket.yaml
-doc/ri/Folio/Socket/new-c.yaml
-doc/ri/Folio/Document
-doc/ri/Folio/Document/write-i.yaml
-doc/ri/Folio/Document/%3c-i.yaml
-doc/ri/Folio/Document/open-i.yaml
-doc/ri/Folio/Document/read-i.yaml
-doc/ri/Folio/Document/cdesc-Document.yaml
-doc/ri/Folio/Document/executable%3f-i.yaml
-doc/ri/Folio/Document/readlines-i.yaml
-doc/ri/Folio/Document/delete-i.yaml
-doc/ri/Folio/Document/intialize-i.yaml
-doc/ri/Folio/Document/%3c%3c-i.yaml
-doc/ri/Folio/Document/unlink-i.yaml
-doc/ri/Folio/Document/truncate-i.yaml
-doc/ri/Folio/Document/document%3f-i.yaml
-doc/ri/Folio/Document/append-i.yaml
-doc/ri/Folio/Document/executable_real%3f-i.yaml
-doc/ri/Folio/FileNotFound
-doc/ri/Folio/FileNotFound/cdesc-FileNotFound.yaml
-doc/ri/Folio/Device
-doc/ri/Folio/Device/cdesc-Device.yaml
-doc/ri/Folio/Device/new-c.yaml
-doc/ri/Folio/BlockDevice
-doc/ri/Folio/BlockDevice/blockdev%3f-i.yaml
-doc/ri/Folio/BlockDevice/cdesc-BlockDevice.yaml
-doc/ri/Folio/CharacterDevice
-doc/ri/Folio/CharacterDevice/chardev%3f-i.yaml
-doc/ri/Folio/CharacterDevice/cdesc-CharacterDevice.yaml
-doc/ri/Folio/Directory
-doc/ri/Folio/Directory/%2b-i.yaml
-doc/ri/Folio/Directory/files-i.yaml
-doc/ri/Folio/Directory/entries-i.yaml
-doc/ri/Folio/Directory/rm_rf-i.yaml
-doc/ri/Folio/Directory/documents-i.yaml
-doc/ri/Folio/Directory/delete-i.yaml
-doc/ri/Folio/Directory/chroot-i.yaml
-doc/ri/Folio/Directory/%2f-i.yaml
-doc/ri/Folio/Directory/directories-i.yaml
-doc/ri/Folio/Directory/directory_entries-i.yaml
-doc/ri/Folio/Directory/chdir-i.yaml
-doc/ri/Folio/Directory/foreach-i.yaml
-doc/ri/Folio/Directory/unlink-i.yaml
-doc/ri/Folio/Directory/document_entries-i.yaml
-doc/ri/Folio/Directory/rmdir-i.yaml
-doc/ri/Folio/Directory/cdesc-Directory.yaml
-doc/ri/Folio/Directory/chown_r-i.yaml
-doc/ri/Folio/Directory/directory%3f-i.yaml
-doc/ri/Folio/Directory/cp_r-i.yaml
-doc/ri/Folio/Directory/rm_r-i.yaml
-doc/ri/Folio/Directory/chmod_r-i.yaml
-doc/ri/Folio/Directory/new-c.yaml
-doc/ri/Folio/Directory/cd-i.yaml
-doc/ri/Folio/cdesc-Folio.yaml
-doc/ri/Enumerator
-doc/ri/Enumerator/cdesc-Enumerator.yaml
-doc/ri/created.rid
-test
-test/test_folio.rb
-test/test_helper.rb
-test/fixture
-test/fixture/foo.txt
-test/fixture/sub
-test/fixture/bar.txt
+doc/book
+doc/book/basedir-spec-0.6.html
 CHANGES
+TODO
 README
-METADATA
+meta
+meta/homepage
+meta/summary
+meta/abstract
+meta/releases
+meta/authors
+meta/contact
 demo
 demo/sample1
 demo/sample1/bar
@@ -240,10 +24,12 @@ lib/folio/pipe.rb
 lib/folio/directory.rb
 lib/folio/device.rb
 lib/folio/errors.rb
+lib/folio/shell.rb
 lib/folio/document.rb
+lib/folio/xdg.rb
 lib/folio/fileobject.rb
 lib/folio/socket.rb
-lib/folio/prompt.rb
 lib/folio.rb
+VERSION
 NEWS
 COPYING

data/NEWS

@@ -1,9 +1,11 @@
-= News & Release Notes
-
-== 0.1.0 // 2008-08-18
-
 Folio was spawned by ruby-talk:311762.
 
-This is the initial release of Folio.
-As such it is very much an alpha release!!!
+Main new feature added with this release is support
+for XDG base directories.
+
+This is the third release since the initial idea.
+Techincally this is still "alpha" code as it needs
+many more tests. Nontheless, the library is a rather
+strightforward wrapper around Ruby internals, so it
+already fairly usable.
 

data/TODO

@@ -0,0 +1,8 @@
+= TODO List
+
+* Could Shell and Directory be unified?
+  * That would make Directory mutable.
+  * It would require two sets of methods, one for shell navigation and one not.
+
+* Need to consider better when to use enumerators vs. returning arrays.
+

data/VERSION

@@ -0,0 +1 @@
+folio 0.3.0 beta (2008-09-16)

data/doc/book/basedir-spec-0.6.html

@@ -0,0 +1,138 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>XDG Base Directory Specification</title><meta name="generator" content="DocBook XSL Stylesheets V1.66.1"></head><body link="#0000ff" alink="#0000ff" bgcolor="white" text="black" vlink="#840084"><div class="article" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="index"></a>XDG Base Directory Specification</h1></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Waldo</span> <span class="surname">Bastian</span></h3><div class="affiliation"><div class="address"><p><br>
+	&nbsp;&nbsp;&nbsp;&nbsp;<tt class="email">&lt;<a href="mailto:bastian@kde.org">bastian@kde.org</a>&gt;</tt><br>
+	&nbsp;&nbsp;</p></div></div></div></div></div><div><p class="releaseinfo">Version 0.6</p></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#introduction">Introduction</a></span></dt><dt><span class="sect1"><a href="#basics">Basics</a></span></dt><dt><span class="sect1"><a href="#variables">Environment variables</a></span></dt><dt><span class="sect1"><a href="#referencing">Referencing this specification</a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="introduction"></a>Introduction</h2></div></div></div><p>
+      Various specifications specify files and file formats. This 
+      specification defines where these files should be looked for by 
+      defining one or more base directories relative to which files 
+      should be located. 
+    </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="basics"></a>Basics</h2></div></div></div><p>
+      The XDG Base Directory Specification is based on the following concepts: 
+      </p><div class="itemizedlist"><ul type="disc"><li><p>
+            There is a single base directory relative to which user-specific
+            data files should be written. This directory is defined by the
+            environment variable <tt class="literal">$XDG_DATA_HOME</tt>.
+          </p></li><li><p>
+            There is a single base directory relative to which user-specific
+            configuration files should be written. This directory is defined by the
+            environment variable <tt class="literal">$XDG_CONFIG_HOME</tt>.
+          </p></li><li><p>
+            There is a set of preference ordered base directories relative to
+            which data files should be searched.  This set of directories is defined
+            by the environment variable <tt class="literal">$XDG_DATA_DIRS</tt>.
+          </p></li><li><p>
+            There is a set of preference ordered base directories relative to
+            which configuration files should be searched.  
+            This set of directories is defined
+            by the environment variable <tt class="literal">$XDG_CONFIG_DIRS</tt>.
+          </p></li><li><p>
+            There is a single base directory relative to which user-specific
+            non-essential (cached) data should be written. 
+            This directory is defined by the
+            environment variable <tt class="literal">$XDG_CACHE_HOME</tt>.
+          </p></li></ul></div><p>
+    </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="variables"></a>Environment variables</h2></div></div></div><p>
+      <tt class="literal">$XDG_DATA_HOME</tt> defines the base directory relative to
+      which user specific data files should be stored. If
+      <tt class="literal">$XDG_DATA_HOME</tt> is either not set or empty, a default equal to
+      <tt class="literal">$HOME</tt>/.local/share should be used.
+    </p><p>
+      <tt class="literal">$XDG_CONFIG_HOME</tt> defines the base directory relative to
+      which user specific configuration files should be stored. If
+      <tt class="literal">$XDG_CONFIG_HOME</tt> is either not set or empty, a default equal to
+      <tt class="literal">$HOME</tt>/.config should be used.
+    </p><p>
+      <tt class="literal">$XDG_DATA_DIRS</tt> defines the preference-ordered set of
+      base directories to search for data files in addition to the 
+      <tt class="literal">$XDG_DATA_HOME</tt> base directory.
+      The directories in <tt class="literal">$XDG_DATA_DIRS</tt> should be seperated 
+      with a colon ':'.
+    </p><p>
+      If <tt class="literal">$XDG_DATA_DIRS</tt> is either not set or empty, a value equal to
+      /usr/local/share/:/usr/share/ should be used. 
+    </p><p>
+      <tt class="literal">$XDG_CONFIG_DIRS</tt> defines the preference-ordered set of
+      base directories to search for configuration files in addition to the 
+      <tt class="literal">$XDG_CONFIG_HOME</tt> base directory.
+      The directories in <tt class="literal">$XDG_CONFIG_DIRS</tt> should be seperated 
+      with a colon ':'.
+    </p><p>
+      If <tt class="literal">$XDG_CONFIG_DIRS</tt> is either not set or empty, a value equal to
+      /etc/xdg should be used. 
+    </p><p>
+      The order of base directories denotes their importance; the first
+      directory listed is the most important. When the same information is
+      defined in multiple places the information defined relative to the more
+      important base directory takes precedent. The base directory defined
+      by <tt class="literal">$XDG_DATA_HOME</tt> is considered more important than 
+      any of the base directories defined by <tt class="literal">$XDG_DATA_DIRS</tt>.
+      The base directory defined
+      by <tt class="literal">$XDG_CONFIG_HOME</tt> is considered more important than
+      any of the base directories defined by <tt class="literal">$XDG_CONFIG_DIRS</tt>.
+    </p><p>
+      <tt class="literal">$XDG_CACHE_HOME</tt> defines the base directory relative to
+      which user specific non-essential data files should be stored. If
+      <tt class="literal">$XDG_CACHE_HOME</tt> is either not set or empty, a default equal to
+      <tt class="literal">$HOME</tt>/.cache should be used.
+    </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both;"><a name="referencing"></a>Referencing this specification</h2></div></div></div><p>
+      Other specifications may reference this specification by specifying the
+      location of a data file as
+      <tt class="literal">$XDG_DATA_DIRS</tt>/subdir/filename. This implies that:
+      </p><div class="itemizedlist"><ul type="disc"><li><p>
+            Such file should be installed to <tt class="literal">$datadir</tt>/subdir/filename
+            with <tt class="literal">$datadir</tt> defaulting to /usr/share.
+          </p></li><li><p>
+            A user specific version of the data file may be created in
+            <tt class="literal">$XDG_DATA_HOME</tt>/subdir/filename, taking into
+            account the default value for <tt class="literal">$XDG_DATA_HOME</tt> if
+            <tt class="literal">$XDG_DATA_HOME</tt> is not set.
+          </p></li><li><p>
+            Lookups of the data file should search for ./subdir/filename relative to
+            all base directories specified by <tt class="literal">$XDG_DATA_HOME</tt> and 
+            <tt class="literal">$XDG_DATA_DIRS</tt> . If an environment 
+            variable is either not set or empty, its default value as defined by this specification 
+            should be used instead.
+          </p></li></ul></div><p>
+    </p><p>
+      Specifications may reference this specification by specifying the
+      location of a configuration file as
+      <tt class="literal">$XDG_CONFIG_DIRS</tt>/subdir/filename. This implies that:
+      </p><div class="itemizedlist"><ul type="disc"><li><p>
+            Default configuration files should be installed to <tt class="literal">$sysconfdir</tt>/xdg/subdir/filename
+            with <tt class="literal">$sysconfdir</tt> defaulting to /etc.
+          </p></li><li><p>
+            A user specific version of the configuration file may be created in
+            <tt class="literal">$XDG_CONFIG_HOME</tt>/subdir/filename, taking into
+            account the default value for <tt class="literal">$XDG_CONFIG_HOME</tt> if
+            <tt class="literal">$XDG_CONFIG_HOME</tt> is not set.
+          </p></li><li><p>
+            Lookups of the configuration file should search for ./subdir/filename relative to
+            all base directories indicated by <tt class="literal">$XDG_CONFIG_HOME</tt> and 
+            <tt class="literal">$XDG_CONFIG_DIRS</tt> . If an environment 
+            variable is either not set or empty, its default value as defined by this specification 
+            should be used instead.
+          </p></li></ul></div><p>
+    </p><p>
+      If, when attempting to write a file, the destination 
+      directory is non-existant an attempt should be made to create it 
+      with permission <tt class="literal">0700</tt>. If the destination directory
+      exists already the permissions should not be changed.
+      The application should be prepared to handle the case where the file 
+      could not be written, either because the directory was non-existant 
+      and could not be created, or for any other reason. In such case it 
+      may chose to present an error message to the user.
+    </p><p>
+      When attempting to read a file, if for any reason a file in a certain
+      directory is unaccessible, e.g. because the directory is non-existant, 
+      the file is non-existant or the user is not authorized to open the file,
+      then the processing of the file in that directory should be skipped. 
+      If due to this a required file could not be found at all, the 
+      application may chose to present an error message to the user.
+    </p><p>
+      A specification that refers to <tt class="literal">$XDG_DATA_DIRS</tt> or 
+      <tt class="literal">$XDG_CONFIG_DIRS</tt> should define what the behaviour 
+      must be when a file is located under multiple base directories. 
+      It could, for example, define that only the file under the most 
+      important base directory should be used or, as another example,
+      it could define rules for merging the information from the different
+      files.
+    </p></div></div></body></html>

data/lib/folio.rb

@@ -1,6 +1,6 @@
 require 'fileutils'
 require 'folio/errors'
-require 'folio/prompt'
+require 'folio/shell'
 require 'folio/fileobject'
 require 'folio/directory'
 require 'folio/document'
@@ -20,16 +20,27 @@ require 'folio/pipe'
 # We use the term `document` instead to mean "regular files".
 # This terminolgy was chosen for two reasons. Namely, (1) a 
 # differentiation in terms was required; and (2) a file in the
-# everyday sense is something in which one puts papars (eg. documents).
-#
+# everyday sense is something in which one puts papars
+# (eg. documents).
+
 module Folio
 
+  #
   def self.file(*path)
     FileObject[*path]
   end
 
-  def self.[](*path)
-    Prompt.new(*path)
+  def self.shell(*path)
+    Shell.new(*path)
+  end
+
+  class << self
+    # Should we have this? 
+    # Perhaps Folio should be the Prompt class?
+    #alias_method :new, :shell
+
+    # Should #[] be alias for #file instead?
+    #alias_method :[], :shell ???
   end
 
 end