13 releases

Uses old Rust 2015

0.1.12 Jun 22, 2016
0.1.11 May 30, 2016
0.1.9 Oct 10, 2015
0.1.8 Aug 1, 2015
0.1.2 May 26, 2015

#506 in Command-line interface

Download history 83/week @ 2023-05-31 25/week @ 2023-06-07 48/week @ 2023-06-14 101/week @ 2023-06-21 68/week @ 2023-06-28 82/week @ 2023-07-05 34/week @ 2023-07-12 70/week @ 2023-07-19 63/week @ 2023-07-26 29/week @ 2023-08-02 48/week @ 2023-08-09 65/week @ 2023-08-16 32/week @ 2023-08-23 39/week @ 2023-08-30 72/week @ 2023-09-06 54/week @ 2023-09-13

197 downloads per month
Used in rustty-oxide

MIT license


rustty: a terminal UI library

Build Status Crates.io Crates.io


Rustty is a terminal UI library that provides a simple, concise abstraction over an underlying terminal device.

Rustty is based on the concepts of cells and events. A terminal display is an array of cells, each holding a character and a set of foreground and background styles. Events are how a terminal communicates changes in its state; events are received from a terminal, processed, and pushed onto an input stream to be read and responded to.


Installation is simple, to use rustty, first add this to your Cargo.toml:

rustty = "*"

Then, add this to your crate root:

extern crate rustty;


The purpose of this section is to introduce and explain the main concepts of rustty and the decisions behind its design.


The terminal representation can be thought of as such:

0-------------------------------cols (x)
rows (y)

Along the x-axis are the columns and along the y-axis are the rows. The upper-left corner is the origin, which begins at index (0, 0) and extends to (cols, rows). Each point (x, y) represents a single cell, which is the next topic.


A cell is a single point on a character display, representing a single character and its foreground and background styles.


Events are how changes in a terminal's state are represented. A terminal has an associated event stream which acts much like a UNIX pipe, or a FIFO queue. When events occur they are pushed on to the back of the stream; when events are read they are taken from the front of the stream.

Usage Guide

Examples and usage suggestions can be found in the API documentation.


If you encounter any issues with the library or have suggestions, please report them with the issue tracker.

If you have any further questions, please don't hesitate to email me, and I respond as soon as I am able.


~89K SLoC