Permalink
Browse files

Remove unused docs

Also add releases to table of contents so as not to generate an unused
warning.

I didn't configuration.rst because it looks like that still needs some porting work.
  • Loading branch information...
1 parent c255494 commit e5cf1698ac35e419505f103bc1ab7212b4b2f4f4 @tych0 tych0 committed Jan 15, 2013
Showing with 2 additions and 115 deletions.
  1. +0 −38 docs/admin.rst
  2. +0 −43 docs/development.rst
  3. +0 −34 docs/faq.rst
  4. +2 −0 docs/index.rst
View
@@ -1,38 +0,0 @@
-=====
-Admin
-=====
-
-Contact
-=======
-
-Please send any comments, suggestions and bug reports to aldo@nullcube.com.
-
-.. mailto:aldo@nullcube.com
-
-
-License
-=======
-
-This project is distributed under the MIT license.
-
-Copyright (c) 2008, Aldo Cortesi
-All rights reserved.
-
-
-Permission is hereby granted, free of charge, to any person obtaining a
-copy of this software and associated documentation files (the "Software"), to
-deal in the Software without restriction, including without limitation the
-rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
-sell copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
- The above copyright notice and this permission notice shall be included in
- all copies or substantial portions of the Software.
-
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
- SOFTWARE.
View
@@ -1,43 +0,0 @@
-================
-Developing Qtile
-================
-
-Using Xephyr and the test suite
-===============================
-
-Qtile has a very extensive test suite, using the Xephyr nested X server. When
-tests are run, a nested X server with a nested instance of Qtile is fired up,
-and then tests interact with the Qtile instance through the client API. The
-fact that we can do this is a great demonstration of just how completely
-scriptable Qtile is. In fact, Qtile is designed expressly to be scriptable
-enough to allow unit testing in a nested environment.
-
-The Qtile repo includes a tiny helper script to let you quickly pull up a
-nested instance instance of Qtile in Xephyr, using your current configuration.
-Run it from the top-level of the repository, like this::
-
- ./test/scripts/xephyr
-
-In practice, the development cycle looks something like this:
-
-#. Make minor code change
-#. Run appropriate tests using ``nosetests``
-#. GOTO 1, until hackage is complete
-#. Run entire test suite
-#. Commit
-
-
-Resources
-=========
-
-Here are a number of resources that may come in handy:
-
-
-* `Inter-Client Conventions Manual`_
-* `Extended Window Manager Hints`_
-* A reasonable basic `Xlib Manual`_
-
-.. _Inter-Client Conventions Manual: http://tronche.com/gui/x/icccm/
-.. _Extended Window Manager Hints: http://standards.freedesktop.org/wm-spec/wm-spec-latest.html
-.. _Xlib Manual: http://tronche.com/gui/x/xlib/
-
View
@@ -1,34 +0,0 @@
-==========================
-Frequently Asked Questions
-==========================
-
-
-When I first start xterm/urxvt/rxvt containing an instance of Vim, I see text and layout corruption. What gives?
-----------------------------------------------------------------------------------------------------------------
-
-Vim is not handling terminal resizes correctly. You can fix the problem by
-starting your xterm with the ``-wf`` option, like so::
-
- xterm -wf -e vim
-
-Alternatively, you can just cycle through your layouts a few times, which
-usually seems to fix it.
-
-
-How do I know which modifier specification maps to which key?
--------------------------------------------------------------
-
-To see a list of modifier names and their matching keys, use the ``xmodmap``
-command. On my system, the output looks like this::
-
- > xmodmap
- xmodmap: up to 3 keys per modifier, (keycodes in parentheses):
-
- shift Shift_L (0x32), Shift_R (0x3e)
- lock Caps_Lock (0x9)
- control Control_L (0x25), Control_R (0x69)
- mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
- mod2 Num_Lock (0x4d)
- mod3
- mod4 Super_L (0xce), Hyper_L (0xcf)
- mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)
View
@@ -76,3 +76,5 @@ Miscellaneous
/manual/ref/index
/manual/ref/*
/manual/*
+ /releases/index
+ /releases/*

0 comments on commit e5cf169

Please sign in to comment.