dvtm || dynamic virtual terminal manager

Tiling window management for the console

menu

• News

• Download

• Why dvtm?

• Development

• Installation

• First steps

• Configuration

• Command line options

• FAQ

• Layouts

• Screenshots

• Links

• License

dvtm

dvtm brings the concept of tiling window management, popularized by X11-window managers like dwm to the console. As a console window manager it tries to make it easy to work with multiple console based programs.

News

• dvtm-0.12 released (05.07.2014)
• dvtm-0.11 released (08.03.2014)
• dvtm-0.10 released (28.12.2013)
• dvtm-0.9 released (3.04.2013)
• dvtm-0.8 released (1.08.2012)
• dvtm-0.7 released (4.09.2011)
• dvtm-0.6 released (8.10.2010)
• dvtm-0.5.2 released (7.07.2009)
• dvtm-0.5.1 released (8.02.2009)
• dvtm-0.5 released (26.01.2009)
• dvtm-0.4.1 released (10.05.2008)
• dvtm-0.4 released (17.02.2008)
• dvtm-0.3 released (12.01.2008)
• dvtm-0.2 released (29.12.2007)
• dvtm-0.1 released (21.12.2007)
• dvtm-0.01 released (08.12.2007)

Download

Download the latest source tarball with sha1sum

1b433db25d9751e820fc8213874eb57fd15e5552 dvtm-0.12.tar.gz

dvtm is packaged by various distributions

• Debian GNU/Linux
• Ubuntu
• Fedora
• openSUSE
• Arch Linux
• Gentoo
• Slackware
• FreeBSD
• NetBSD
• OpenBSD
• Mac OS X (homebrew)

dvtm also has a freshmeat.net project page and is listed onohloh.

Why dvtm?

dvtm strives to adhere to the Unix philosophy. It tries to do one thing, dynamic window management on the console, and to do it well. For example dvtm does not implement session management but instead delegates this task to a separate tool called abduco. As a result dvtm's source code is relatively small (~4000 lines of ANSI C), simple and therefore easy to hack on.

Development

You can always fetch the current codebase from the git repository.

git clone git://repo.or.cz/dvtm.git

If you have comments, suggestions, ideas, a bug report, a patch or something else related to dvtm then write to thesuckless.org development maling list (the list members don't mind) or contact me directly mat[at]brain-dump.org.

Installation

In order to use dvtm you will need a curses library, for example libncurses.

Download the latest version of dvtm and extract it. Edit config.mk to match your local setup (dvtm is installed into the /usr/local namespace by default). Customize config.h as you see fit, see the configuration section for further information.

If you are on a system with UTF-8 locales (if unsure check $LANG and the output of locale) you probably want dvtm to be linked against libncursesw (the default) otherwise change config.mk to link against plain libncurses.

$EDITOR config.mk$EDITOR config.hmakemake install

You should now be able to start dvtm, redirect stderr to a file or /dev/null (just in case something goes wrong you will see it there).

./dvtm 2> log

First steps / Introduction tutorial

All of dvtm keybindings start with a common modifier which from now on is refered to as MOD. By default MOD is set toCTRL+g however this can be changed at runttime with the -mcommand line flag or at compile time by changing config.h.

After starting dvtm create a few windows by pressing MOD+c. Now open the dvtm manual page with MOD+? and read through it. Start switching between the different windows with MOD+j and MOD+k or directly with MOD+1 to MOD+9 where the digit corresponds to the window number which is displayed in the titlebar. Bring a different window to the master area with MOD+Enter. Try experimenting with differentlayouts by cycling through them with MOD+Space. Minimize unimportant windows with MOD+. issuing the command a second time restores the window. To forcably close a window use MOD+x. dvtm will automatically terminate once the last window is closed. If you want to quit earlier use MOD+q.

Configuration

The configuration of dvtm is done by creating a customconfig.h and (re)compiling the source code. See the defaultconfig.def.h as an example adapting it to your preference should be straightforward. You basically define a set of layouts and keys which dvtm will use. There are some pre defined macros to ease configuration.

Command line options

dvtm only contains a few simple command line options, the most important ones are briefly described below. Consult the manual page for the complete documentation.

• -v prints the version and exits
• -m mod sets the modifier during runtime and thus overrides settings in config.h. So -m ^w will set the modifier toCTRL+w. This might be useful if you want to run multiple nested dvtm instances.
• -s status-fifo if status-fifo is a valid named pipe dvtm will read it's content and display it in the statusbar. See the dvtm-status script below which is also included in the source tarball for a possible usecase.

#!/bin/shFIFO="/tmp/dvtm-status.$$"[ -e "$FIFO" ] || mkfifo "$FIFO"chmod 600 $FIFOwhile true; dodate +%H:%Msleep 60done > $FIFO &STATUS_PID=$!./dvtm -s $FIFO 2> /dev/nullkill $STATUS_PIDrm $FIFO

FAQ

Below are some explanations to topics which were asked quite frequently.

Detach / reattach functionality

dvtm in combination with abduco serves as an alternative to tmux or screen.

abduco -c dvtm-session

Similar to abduco you can also use use dtach.

dtach -c /tmp/dvtm-session -r winch dvtm

WARNING: terminal is not fully functional

This means you haven't installed the dvtm.info terminfo description which can be done with tic -s dvtm.info. If for some reason you can't install new terminfo descriptions set the DVTM_TERM environment variable to a known terminal when starting dvtm

DVTM_TERM=rxvt dvtm

The window title remains empty

Why does the current directory not show up in the window title as seen on the screenshots below? First of all the dynamic title is a xterm extension and works via the following escape sequence:

echo -ne "\033]0;Your title here\007"

The effect of the screenshot can be achieved by means of a shell feature which executes a given command every time the prompt is redrawn. In bash this can be accomplished by an environment variable called PROMPT_COMMAND. You should therefore check your shell startup files for a section like this and add dvtm to the corresponding conditional expression.

# If this is an xterm set the title to user@host:dircase "$TERM" indvtm*|xterm*|rxvt*)    PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD/$HOME/~}\007"'    ;;*)    ;;esac

Other shells provide similar functionality, zsh as an example has a precmd function which can be used to achieve the same effect.

Something is wrong with the displayed colors

Make sure you have set $TERM correctly for example if you want to use 256 color profiles you probably have to append-256color to your regular terminal name. Also due to limitations of ncurses by default you can only use 255 color pairs simultaneously. If you need more than 255 different color pairs at the same time, then you have to rebuild ncurses with

./configure ... --enable-ext-colors

Note that this changes the ABI and therefore sets SONAME of the library to 6 (i.e. you have to link againstlibncursesw.so.6).

Some characters are displayed like garbage

Make sure you compiled dvtm against a unicode aware curses library (in case of ncurses this would be libncursesw). Also make sure that your locale settings contain UTF-8.

Copy / Paste doesn't work under X

If you have mouse support enabled, which is the case with the default settings, you need to hold down shift while selecting and inserting text. In case you don't like this behaviour either run dvtm with the -M command line argument, disable it a run time with MOD+M or removeCONFIG_MOUSE from the CFLAGS in config.mk you will however no longer be able to perform other mouse actions like selecting windows etc.

The numeric keypad doesn't work with Putty

Disable application keypad mode in the Putty configuration under Terminal => Features => Disable application keypad mode.

Unicode characters don't work within Putty

You have to tell Putty in which character encoding the received data is. Set the dropdown box under Window => Translation to UTF-8. In order to get proper line drawing characters you proabably also want to set the TERMenvironment variable to putty or putty-256color. If that still doesn't do the trick then try running dvtm with the following ncurses related environment variable setNCURSES_NO_UTF8_ACS=1.

Problems with some readline keybindings

Pressing CTRL+j j/k to view the command line history doesn't work, it behaves like ENTER. This is the case for all curses applications because curses uses the keybindings as defined by terminfo and CTRL+j is normally configured to match the ENTER behaviour. This can be verified with infocmp.

infocmp $TERM | grep '\^J'   cud=\E[%p1%dB, cud1=^J, cuf=\E[%p1%dC, cuf1=\E[C,   il=\E[%p1%dL, il1=\E[L, ind=^J, is1=\E[?47l\E=\E[?1l,

As you can see ^J is mapped to cud1 and ind which acorrding to terminfo(5) means line down respectively scroll text up. This means dvtm will never see CTRL+j but instead allways receive KEY_ENTER.

Layouts

dvtm currently uses 4 layouts in its default configuration.

• Vertical Stack Tiling (default)

  the left half of the screen (master area) is used by the currently focused window the remaining windows are stacked on the right half of the screen

• Bottom Stack Tiling

  top half is the master area bottom half is for the remaining windows

• Grid

  every window gets an equally sized portion of the screen

• Fullscreen

  only the selected window is shown and occupies the whole available display area

Included in the tarball but not used in the default configuration are also

• Top Stack Tiling

  the master area is in the bottom half of the screen, the remaining windows in the top half

• Spiral

• Dwindle

Screenshots

Below are a few screenshots which show dvtm in action. 

 

Links

Below are some links which are in one way or another related to dvtm.

• dwm
• tmux

License

dvtm reuses some code of dwm and is released under the same MIT/X11 license. The terminal emulation part is licensed under the ISC license.