90 stable releases

new 2.3.12 Jul 29, 2021
2.3.7 Jun 29, 2021
2.2.4 Mar 28, 2021
2.1.3 Dec 31, 2020
1.2.4 Mar 24, 2020

#51 in Command-line interface

Download history 100/week @ 2021-04-08 159/week @ 2021-04-15 32/week @ 2021-04-22 150/week @ 2021-04-29 56/week @ 2021-05-06 147/week @ 2021-05-13 19/week @ 2021-05-20 13/week @ 2021-05-27 26/week @ 2021-06-03 125/week @ 2021-06-10 24/week @ 2021-06-17 65/week @ 2021-06-24 37/week @ 2021-07-01 36/week @ 2021-07-08 127/week @ 2021-07-15 19/week @ 2021-07-22

280 downloads per month
Used in 2 crates



Crate API MSRV: 1.48.0

libnotcurses-sys is a low-level Rust wrapper for the notcurses C library

This library is built with several layers of zero-overhead abstractions over the C functions and pointers accessed through FFI.

How to use this library

There are basically two ways: The Rust way, and the C way. (Or a mix of both).

1. The Rust way

Where you use the more safely wrapped types, with its methods and constructors, and painless error handling, like this:

use libnotcurses_sys::*;

fn main() -> NcResult<()> {
    let mut nc = Nc::with_flags(NCOPTION_NO_ALTERNATE_SCREEN)?;
    let plane = nc.stdplane();
    plane.putstr("hello world")?;

Although you still have to manually call the stop() method for Nc and NcDirect objects, and the destroy() method for the rest of types that allocate, (like NcPlane, NcMenu…) at the end of their scope, since the Drop trait is not implemented for any wrapping type in libnotcurses-sys.

But they do implement methods and use NcResult as the return type, for handling errors in the way we are used to in Rust.

For the types that don't allocate, most are based on primitives like i32, u32, u64… without a name in the C library. In Rust they are type aliased (e.g.: NcChannel, NcChannelPair, NcRgb, NcColor…), to leverage type checking, and they implement methods through traits (e.g. NcChannelMethods must be in scope to use the NcChannel methods.

2. The C way

You can always use the C API functions directly if you prefer, in a very similar way as the C library is used.

It requires the use of unsafe, since most functions are wrapped directly by bindgen marked as such.

Error handling is done this way by checking the returned NcIntResult, or in case of receiving a pointer, by comparing it to null_mut().


use core::ptr::{null, null_mut};
use std::process::exit;

use libnotcurses_sys::*;

fn main() {
    let options = ffi::notcurses_options {
        termtype: null(),
        renderfp: null_mut(),
        loglevel: 0,
        margin_t: 0,
        margin_r: 0,
        margin_b: 0,
        margin_l: 0,
    unsafe {
        let nc = notcurses_init(&options, null_mut());
        if nc == null_mut() {
        let plane = notcurses_stdplane(nc);
        let cols = ncplane_putstr(&mut *plane, "hello world");
        if cols < NCRESULT_OK {
        if notcurses_stop(nc) < NCRESULT_OK {

The notcurses C API docs


~31K SLoC