Howm is on the AUR, there are two packages for it:
- howm-x11-git is the bleeding edge package.
- howm-x11 is the package based off of stable releases.
Come and join us on Freenode in the channel #howm
- Contributing
- Requirements
- Installation
- Commandline Arguments
- Configuration
- Changing Socket Path
- Keybinds
- Scratchpad
- Motions
- Counts
- Operators
- Modes
- Code Documentation
- Parsing Output
- Cottage is required for configuration and interacting with howm.
- sxhkd is required for binding cottage commands to keypress.
Howm is on the AUR, there are two packages for it:
If you can't use the AUR, then there may be a package available for your distro.
As a last resort install xcb's libraries and then, do the following:
git clone https://github.com/HarveyHunt/howm
cd howm
make
sudo make installAfter howm is installed, you'll want to copy over some configuration files.
cp examples/sxhkdrc_* ~/.config/sxhkd
cp examples/howmrc ~/.config/howmrcThen take a look at the example xinitrc for ideas on how to start howm.
Be sure to install cottage and sxhkd.
- -c: The path that points to an executable howmrc file.
howm -c ~/.config/howm/howmrc
Configuration is done through the use of cottage. Any element in this structure can be changed using cottage. The syntax is as follows:
cottage -c config_var value
For example:
cottage -c bar_height 20
To override howm's default values at startup, cottage commands can be placed in a shell script and then executed by howm. Take a look at the example howmrc for ideas.
Note: When configuring colours in howmrc, enclose the colour in quotes, such as:
cottage -c border_focus "#343434"
By default, howm will attempt to create a socket at /tmp/howm, this can be overwritten by setting the environment variable HOWM_SOCK. For example:
export HOWM_SOCK=/tmp/howm_testKeybinds are now placed in multiple sxhkd files.
A keypress is bound to a call to cottage in the following form:
cottage -f func_name <args>
All of the available functions can be found here. Take a look at the example sxhkdrcs.
The scratchpad is a location to store a single client out of view. When requesting a client back from the scratchpad, it will float in the center of the screen. This is useful for keeping a terminal handy or hiding your music player- only displaying it when it is really needed.
The size of the scratchpad's client is defined by SCRATCHPAD_WIDTH and SCRATCHPAD_HEIGHT.
For a good primer on motions, vim's documentation explains them well.
Please note: The modifier key that is OTHER_MOD needs to be held down whilst entering a motion.
Operators and motions are combined so that an operation can be performed on multiple things, such as clients or workspaces. The current supported motions are as follows:
-
Workspace: Perform an operation on one or more workspaces.
-
Client: Perform an operation on one or more clients.
Counts be applied to a motion, to make an operator affect multiple things. For example, you can add a 3 before a motion, meaning that the operator will affect 3 of the motions. The modifier that is used is defined by COUNT_MOD.
For example:
q2w
Will kill 2 workspaces (assuming the correct modifier keys are pressed and default keybindings are being used).
Operators perform an action upon one or more targets (identified by motions).
Implementation details for all operators can be found here.
Below are descriptions of each operator, the motions that they can perform an action upon and the mode that they work in (Note, all examples assume that the correct modifier keys have been pressed and use the default keymappings.):
-
op_kill: An operator that kills an arbitrary number of targets. Can be used on:
- Clients
- Workspaces
Used in mode:
- Normal
q4c
The above command will kill 4 clients, closing the applications and removing them from the workspace.
qw
The above command will kill one workspace. This means that all clients on the current workspace will be killed.
-
op_move_down: An operator that moves a group of targets down one. Can be used on:
- Clients
Used in mode:
- Normal
j2c
The above command moves 2 clients down one place in the workspace's client list. If a client is moved past the last place, then it is wrapped around and placed at the start of the workspace's client list.
-
op_move_up: This is the opposite of op_move_down, and instead is bound to k.
-
op_shrink_gaps: An operator to shrink the size of the gaps around windows. The size is changed by the amount defined for OP_GAP_SIZE. Can be used on:
- Clients
- Workspaces
Used in mode:
- Normal
g1w
The above command will shrink the gaps of all windows on the current workspace by OP_GAP_SIZE.
g4c
The above command will shrink the gaps of 4 clients on the current workspace by OP_GAP_SIZE.
-
op_grow_gaps: This is the opposite of op_shrink_gaps and is bound to Shift + g.
-
op_focus_up: Move the current focus up. Can be used on:
- Clients
- Workspaces
Used in mode:
- Focus
j3c
The above command will move the current focus down 3 clients.
-
op_focus_down: Performs the opposite of op_focus_up and is instead bound to j.
-
op_cut: Cut a group of clients or workspaces and store them on the delete register stack. Can be used on:
- Clients
- Workspaces
Used in mode:
- Normal
d2c
The above command will cut 2 clients and place them onto the delete register stack. One use of the cut operation takes up one place on the stack.
A good primer on modes is available here.
Note: Modes used to be implemented in howm itself, but are now in the sxhkd configuration file.
In howm, modes are used to allow the same keys to be bound to multiple functions. Modes also help to logically separate what needs to be done to a window. The available modes are as follows:
-
Normal: This mode is the one that you will spend most of your time in. It is used for executing commands and most of the operators are designed to work in this mode. This mode behaves similarly to how other WMs behave, but without focusing or dealing with floating windows.
-
Focus: This mode is designed to be used to change the focus and locations of windows or workspaces.
-
Floating: This mode is designed to deal with all things floating. Moving, resizing and teleporting floating windows are all available in this mode.
howm uses doxygen throughout the entire codebase. The generated documentation is available here.
When debug mode is disabled, howm outputs information about its current state and the current workspace whenever something changes (such as adding a new window). When debug mode is enabled, information is outputted for each workspace (placed on a new line).
The format for the output is as follows:
Layout:Workspace:State:NumberofClients:MonitorIndex
An example output can be seen below:
2:1:0:1:0
The information outputted at the same time as the example above, but with debugging mode turned on is shown below:
2:1:0:1:0
2:2:0:0:0
2:3:0:0:0
2:4:0:0:0
2:5:0:0:0
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent