14 releases (9 breaking)

Uses old Rust 2015

0.13.0 Apr 20, 2020
0.12.2 Dec 15, 2018
0.12.1 Nov 6, 2018
0.10.0 Apr 8, 2018
0.4.0 Jul 24, 2017

#626 in Command-line interface

Download history 86/week @ 2024-03-11 50/week @ 2024-03-18 14/week @ 2024-03-25 88/week @ 2024-04-01 33/week @ 2024-04-08 41/week @ 2024-04-15 66/week @ 2024-04-22 32/week @ 2024-04-29 39/week @ 2024-05-06 45/week @ 2024-05-13 53/week @ 2024-05-20 54/week @ 2024-05-27 57/week @ 2024-06-03 50/week @ 2024-06-10 56/week @ 2024-06-17 59/week @ 2024-06-24

229 downloads per month
Used in 3 crates

Zlib license

504 lines

License:0BSD CratesIO Travis-ci Appveyor


A rust crate to smooth over the pain points of working with curses. Because it's based on pancurses, it works equally well with on both windows and unix computers.

Examples are available in the examples/ directory. The files are somewhat commented, and you can run any of them with cargo to see them in action.

cargo run --example <fileName>

Full API documentation available at docs.rs/easycurses

Terminal Safety

Normally when you're using curses there's a big danger that your program will leave the terminal in an unusable state where things don't print properly and stuff if your program exits on accident and you don't get your chance to call endwin properly. EasyCurses will safely cleanup the terminal and restore it to a useable state when your program closes via its Drop trait. No worries.

The catch is that you do have to only ever have one EasyCurses value active at once. Having two at once would let the initialization and shutdown get out of balance, and things would go bad. This is tracked with an AtomicBool value that's flipped on and off as appropriate.

Similarly, if you ever abort the program entirely there's no chance for cleanup, since an abort is an instant termination of the process. So, just don't ever compile with panic=abort, or use exit, or panic during an unwind, or anything else like that. At least not while an EasyCurses value is in scope somewhere within your call stack.


I would characterize the library as "largely stable". As laid out somewhere during the 1.0-level crate discussions, a crate can't rightly call itself 1.0 unless all the things it depends on are themselves 1.0, so no matter what this crate won't actually go to 1.0 before pancurses does.


This project is released into the public domain via The Unlicense. You are free to use it however you like with or without attribution. If you wish to contribute to the project then you must add your contributions under the same license.


~15K SLoC