Permalink
Browse files

Merge remote-tracking branch 'anshumanb/experimental'

  • Loading branch information...
2 parents b46481b + 62ec39d commit 2d537f33b35c60e608036dac5a9e85e296f554ea @paradoxxxzero paradoxxxzero committed Feb 24, 2012
View
@@ -1,35 +0,0 @@
-
-
-<h2>Contact</h2>
-
-<p> Please send any comments, suggestions and bug reports to
- <a href="mailto:aldo@nullcube.com">aldo@nullcube.com</a>.
-</p>
-
-<h2>License</h2>
-
-<p>This project is distributed under the MIT license. </p>
-
-<hr>
-
-<p> Copyright (c) 2008, Aldo Cortesi<br>
-All rights reserved.</p>
-
-
-<p> 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:</p>
-
-<p> The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.</p>
-
-<p> 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.</p>
View
@@ -1,45 +0,0 @@
-
-Qtile is configured in Python. A script (~/.config/qtile/config.py by default) is
-evaluated, and a small set of configuration variables are pulled from its
-global namespace.
-
-# Variables
-
-## @!linkTo("groups.html")!@
-
-A list of __libqtile.manager.Group__ objects which defines the group names.
-
-## @!linkTo("keys.html")!@
-
-A list of __libqtile.manager.Key__ objects which defines the keybindings. At a
-minimum, this will probably include bindings to switch between windows, groups
-and layouts.
-
-## @!linkTo("layouts.html")!@
-
-A list layout objects, configuring the layouts you want to use.
-
-## __main__
-
-A function that executes after the window manager is initialized, but before
-groups, screens and other components are set up. There are few reasons to use
-this, other than testing and debugging.
-
-
-## @!linkTo("mouse.html")!@
-
-A list of __libqtile.manager.Drag__ and __libqtile.manager.Click__ objects
-defining mouse operations.
-
-
-## @!linkTo("screens.html")!@
-
-A list of __libqtile.manager.Screen__ objects, which defines the physical
-screens you want to use, and the bars and widgets associated with them. Most of
-the visible "look and feel" configuration will happen in this section.
-
-
-# Complete example
-
-$!examples.py("examples/config/cortesi-config.py")!$
-
@@ -1,18 +0,0 @@
-
-The __groups__ config file variable should be initialized to a list of Group
-objects.
-
-$!confobj("libqtile.manager.Group")!$
-
-
-# Example
-
-<!--(block | pySyntax)-->
-from libqtile.manager import Group
-groups = [
- Group("a"),
- Group("b"),
- Group("c"),
-]
-<!--(end)-->
-
@@ -1,22 +0,0 @@
-
-Qtile has an extensive set of hooks that users can bind functions to. Be
-careful when writing hooks - they run in the context of the Qtile process, and
-have complete access to all of Qtile's internal object APIs. This means they
-can be arbitrarily powerful, but they can also crash Qtile or corrupt its data
-structures.
-
-Normally, hooks are subscribed to in the Qtile configuration file. Hooks are
-exposed on the __hook.subscribe__ object. The following code will print the
-client name to stderr (which will show up in your .xsession-errors file)
-whenever focus changes.
-
-<!--(block | pySyntax)-->
-from libqtile import hook
-
-def mymethod(c):
- print >> sys.stderr, c.name
-
-hook.subscribe.client_focus(mymethod)
-<!--(end)-->
-
-$!hookobj("libqtile.hook.Subscribe")!$
@@ -1,38 +0,0 @@
-
-The __keys__ variable defines Qtile's key bindings.
-
-
-$!confobj("libqtile.manager.Key")!$
-
-
-# The command.lazy object
-
-__command.lazy__ is a special helper object to specify a command for later
-execution. This object acts like the root of the object graph, which means that
-we can specify a key binding command with the same syntax used to call the
-command through a script or through [qsh](@!urlTo("qsh.html")!@).
-
-
-# Example
-
-<!--(block | pySyntax)-->
-from libqtile.manager import Key
-keys = [
- Key(
- ["mod1"], "k",
- command.lazy.layout.down()
- ),
- Key(
- ["mod1"], "j",
- lazy.layout.up()
- )
-]
-<!--(end)-->
-
-On my system __mod1__ is the Alt key - you can see which modifiers map to which
-keys on your system by running the __xmodmap__ command. This example binds
-__Alt-k__ to the "down" command on the current layout. This command is standard
-on all the included layouts, and switches to the next window (where "next" is
-defined differently in different layouts). The matching "up" command switches
-to the previous window.
-
@@ -1,31 +0,0 @@
-
-A layout is an algorithm for laying out windows in a group on your screen.
-Since Qtile is a tiling window manager, this usually means that we try to use
-space as efficiently as possible, and give the user ample commands that can be
-bound to keys to interact with layouts.
-
-The __layouts__ variable defines the list of layouts you will use with Qtile.
-The first layout in the list is the default. If you define more than one
-layout, you will probably also want to define key bindings to let you switch to
-the next and previous layouts.
-
-# Built-in layouts
-
-$!confobj("libqtile.layout.Max")!$
-
-$!confobj("libqtile.layout.Stack")!$
-
-$!confobj("libqtile.layout.Tile")!$
-
-
-# Example
-
-
-<!--(block | pySyntax)-->
-from libqtile import layout
-layouts = [
- layout.Max(),
- layout.Stack(stacks=2)
-]
-<!--(end)-->
-
@@ -1,22 +0,0 @@
-
-The __mouse__ config file variable defines a set of global mouse actions, and
-is a list of __Click__ and __Drag__ objects..
-
-$!confobj("libqtile.manager.Click")!$
-
-$!confobj("libqtile.manager.Drag")!$
-
-
-# Example
-
-<!--(block | pySyntax)-->
-from libqtile.manager import Click, Drag
-mouse = [
- Drag([mod], "Button1", lazy.window.set_position_floating(),
- start=lazy.window.get_position()),
- Drag([mod], "Button3", lazy.window.set_size_floating(),
- start=lazy.window.get_size()),
- Click([mod], "Button2", lazy.window.bring_to_front())
-]
-<!--(end)-->
-
@@ -1,75 +0,0 @@
-
-The __screens__ configuration variable is where the physical screens, their
-associated __bars__, and the __widgets__ contained within the bars are defined.
-
-
-# screens
-
-$!confobj("libqtile.manager.Screen")!$
-
-# bars
-
-$!confobj("libqtile.bar.Bar")!$
-
-$!confobj("libqtile.bar.Gap")!$
-
-
-# widgets
-
-$!confobj("libqtile.widget.Clock", "clock.png")!$
-
-$!confobj("libqtile.widget.GroupBox", "groupbox.png")!$
-
-$!confobj("libqtile.widget.AGroupBox")!$
-
-$!confobj("libqtile.widget.Prompt")!$
-
-$!confobj("libqtile.widget.Sep")!$
-
-$!confobj("libqtile.widget.Spacer")!$
-
-$!confobj("libqtile.widget.Systray", "systray.png")!$
-
-$!confobj("libqtile.widget.TextBox")!$
-
-$!confobj("libqtile.widget.WindowName")!$
-
-## Graphs
-
-<img src="@!urlTo('graph.png')!@"/>
-
-$!confobj("libqtile.widget.CPUGraph")!$
-
-$!confobj("libqtile.widget.MemoryGraph")!$
-
-$!confobj("libqtile.widget.SwapGraph")!$
-
-
-# Example
-
-Tying together screens, bars and widgets, we get something like this:
-
-<!--(block|pySyntax)-->
-from libqtile.manager import Screen
-from libqtile import bar, widget
-screens = [
- Screen(
- bottom = bar.Bar(
- [
- widget.GroupBox(),
- widget.WindowName()
- ],
- 30,
- ),
- ),
- Screen(
- bottom = bar.Bar(
- [
- widget.GroupBox(),
- widget.WindowName()
- ],
- 30,
- ),
- )
-]
-<!--(end)-->
View
@@ -1,37 +0,0 @@
-
-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 probelm by
-starting your xterm with the "-wf" option, like so:
-
-<pre>
- xterm -wf -e vim
-</pre>
-
-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:
-
-<pre>
-> 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)
-</pre>
-
-
-
Oops, something went wrong.

0 comments on commit 2d537f3

Please sign in to comment.