Top Related Projects
Quick Overview
Rustyline is a readline implementation in Rust, inspired by Python's readline. It provides line editing functionality with history and completion support, making it useful for building command-line interfaces and interactive shells in Rust applications.
Pros
- Written in pure Rust, offering memory safety and performance benefits
- Supports cross-platform functionality (Windows, macOS, Linux)
- Provides customizable key bindings and completion behavior
- Actively maintained with regular updates and improvements
Cons
- May have a steeper learning curve compared to simpler input libraries
- Documentation could be more comprehensive for advanced use cases
- Limited to command-line applications, not suitable for GUI environments
- Some features may not be as mature as long-standing C libraries like GNU Readline
Code Examples
- Basic usage:
use rustyline::error::ReadlineError;
use rustyline::Editor;
fn main() {
let mut rl = Editor::<()>::new();
loop {
let readline = rl.readline(">> ");
match readline {
Ok(line) => {
println!("Line: {}", line);
rl.add_history_entry(line.as_str());
},
Err(ReadlineError::Interrupted) => {
println!("CTRL-C");
break
},
Err(ReadlineError::Eof) => {
println!("CTRL-D");
break
},
Err(err) => {
println!("Error: {:?}", err);
break
}
}
}
}
- Using custom completion:
use rustyline::completion::{Completer, Pair};
use rustyline::Context;
use rustyline::Editor;
struct MyCompleter;
impl Completer for MyCompleter {
type Candidate = Pair;
fn complete(&self, line: &str, pos: usize, _ctx: &Context<'_>) -> Result<(usize, Vec<Pair>), ReadlineError> {
let commands = vec!["help", "quit", "list"];
let matches: Vec<Pair> = commands
.iter()
.filter(|cmd| cmd.starts_with(line))
.map(|cmd| Pair {
display: cmd.to_string(),
replacement: cmd.to_string(),
})
.collect();
Ok((0, matches))
}
}
fn main() {
let mut rl = Editor::new();
rl.set_completer(Some(MyCompleter));
// ... rest of the code
}
- Customizing key bindings:
use rustyline::config::Config;
use rustyline::Editor;
use rustyline::KeyEvent;
use rustyline::KeyCode;
use rustyline::Modifiers;
fn main() {
let config = Config::builder()
.keyseq_timeout(0)
.edit_mode(rustyline::EditMode::Emacs)
.build();
let mut rl = Editor::with_config(config);
rl.bind_sequence(KeyEvent(KeyCode::Char('f'), Modifiers::CTRL), rustyline::Cmd::ForwardChar);
rl.bind_sequence(KeyEvent(KeyCode::Char('b'), Modifiers::CTRL), rustyline::Cmd::BackwardChar);
// ... rest of the code
}
Getting Started
To use Rustyline in your Rust project, add the following to your Cargo.toml
:
[dependencies]
rustyline = "10.0.0"
Then, in your Rust code:
use rustyline::error::ReadlineError;
use rustyline::Editor;
fn main() {
let mut rl = Editor::<()>::new();
if rl.readline(">> ").is_ok() {
println!("It works!");
}
}
This basic example sets up Rustyline and prompts the user for input.
Competitor Comparisons
Build terminal user interfaces and dashboards using Rust
Pros of tui-rs
- Offers a comprehensive framework for building complex terminal user interfaces
- Supports advanced features like custom widgets and layouts
- Provides a more flexible and powerful approach to TUI development
Cons of tui-rs
- Steeper learning curve compared to Rustyline's simpler API
- Requires more code and setup for basic input scenarios
- May be overkill for simple command-line applications
Code Comparison
Rustyline (basic input):
use rustyline::Editor;
let mut rl = Editor::<()>::new();
let readline = rl.readline(">> ");
match readline {
Ok(line) => println!("Line: {}", line),
Err(_) => println!("Error"),
}
tui-rs (basic input):
use tui::{backend::CrosstermBackend, Terminal};
use crossterm::{event::{self, Event, KeyCode}};
let mut terminal = Terminal::new(CrosstermBackend::new(std::io::stdout()))?;
terminal.draw(|f| {
// Draw UI components
})?;
if let Event::Key(key) = event::read()? {
if key.code == KeyCode::Char('q') {
break;
}
}
The code comparison demonstrates that tui-rs requires more setup and boilerplate for basic input scenarios, while Rustyline provides a simpler API for command-line input. However, tui-rs offers greater flexibility and power for building complex terminal interfaces.
Cross platform terminal library rust
Pros of crossterm
- More comprehensive terminal manipulation capabilities, including cursor movement, colors, and styles
- Cross-platform support for Windows, macOS, and Linux
- Active development with frequent updates and improvements
Cons of crossterm
- Steeper learning curve due to more extensive API
- May be overkill for simple line editing tasks
- Requires more setup and configuration for basic functionality
Code comparison
rustyline:
use rustyline::Editor;
let mut rl = Editor::<()>::new();
let readline = rl.readline(">> ");
match readline {
Ok(line) => println!("Line: {}", line),
Err(_) => println!("Error"),
}
crossterm:
use crossterm::{execute, cursor, terminal, Result};
use std::io::{stdout, Write};
fn main() -> Result<()> {
execute!(stdout(), terminal::Clear(terminal::ClearType::All))?;
execute!(stdout(), cursor::MoveTo(0, 0))?;
print!(">> ");
stdout().flush()?;
Ok(())
}
While rustyline focuses on providing a simple line editing experience, crossterm offers more extensive terminal control capabilities. rustyline is easier to use for basic input scenarios, while crossterm provides greater flexibility for complex terminal applications at the cost of increased complexity.
☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
Pros of Starship
- More feature-rich and customizable prompt system
- Actively maintained with frequent updates
- Supports a wide range of programming languages and tools
Cons of Starship
- Larger project scope, potentially more complex to contribute to
- May have higher system resource usage due to its extensive features
Code Comparison
Rustyline (basic readline implementation):
use rustyline::error::ReadlineError;
use rustyline::Editor;
fn main() {
let mut rl = Editor::<()>::new();
loop {
let readline = rl.readline(">> ");
match readline {
Ok(line) => println!("Line: {}", line),
Err(ReadlineError::Interrupted) => break,
Err(ReadlineError::Eof) => break,
Err(err) => {
println!("Error: {:?}", err);
break;
}
}
}
}
Starship (prompt configuration):
[character]
success_symbol = "[➜](bold green)"
error_symbol = "[✗](bold red)"
[git_branch]
symbol = "🌱 "
truncation_length = 4
truncation_symbol = ""
[package]
symbol = "📦 "
[nodejs]
symbol = "⬢ "
While Rustyline focuses on providing a readline implementation, Starship offers a highly customizable prompt system with support for various programming environments and tools. Rustyline may be more suitable for simpler command-line applications, while Starship is designed for enhancing terminal productivity across multiple shells and platforms.
Terminal based "The Matrix" like implementation
Pros of cmatrix
- Visual appeal: Creates an eye-catching Matrix-like animation in the terminal
- Lightweight: Minimal system resources required for operation
- Customizable: Offers various color options and animation speeds
Cons of cmatrix
- Limited functionality: Primarily a visual effect without practical use cases
- Less versatile: Focused on a single animation style, unlike Rustyline's broad input handling capabilities
Code Comparison
cmatrix (C):
for (j = 0; j <= LINES; j++) {
for (i = 0; i <= COLS - 1; i += 2) {
move(j, i);
if (matrix[i][j].val == 1) {
attrset(COLOR_PAIR(matrix[i][j].color));
addch(matrix[i][j].ascii);
}
}
}
Rustyline (Rust):
pub fn readline(&mut self, prompt: &str) -> Result<String> {
let mut cmd = EditCommand::BeginningOfLine;
let mut line = String::new();
self.move_cursor_to_end();
self.refresh_line()?;
loop {
match self.next_cmd(prompt, &mut cmd)? {
// ... (command handling logic)
}
}
}
The code snippets highlight the different focus areas of each project. cmatrix deals with terminal graphics and animation, while Rustyline handles complex input processing and line editing functionality.
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
RustyLine
Readline implementation in Rust that is based on Antirez' Linenoise
Supported Platforms
- Unix (tested on FreeBSD, Linux and macOS)
- Windows
- cmd.exe
- Powershell
Note:
- Powershell ISE is not supported, check issue #56
- Mintty (Cygwin/MinGW) is not supported
- Highlighting / Colors are not supported on Windows < Windows 10 except with ConEmu and
ColorMode::Forced
.
Example
use rustyline::error::ReadlineError;
use rustyline::{DefaultEditor, Result};
fn main() -> Result<()> {
// `()` can be used when no completer is required
let mut rl = DefaultEditor::new()?;
#[cfg(feature = "with-file-history")]
if rl.load_history("history.txt").is_err() {
println!("No previous history.");
}
loop {
let readline = rl.readline(">> ");
match readline {
Ok(line) => {
rl.add_history_entry(line.as_str());
println!("Line: {}", line);
},
Err(ReadlineError::Interrupted) => {
println!("CTRL-C");
break
},
Err(ReadlineError::Eof) => {
println!("CTRL-D");
break
},
Err(err) => {
println!("Error: {:?}", err);
break
}
}
}
#[cfg(feature = "with-file-history")]
rl.save_history("history.txt");
Ok(())
}
crates.io
You can use this package in your project by adding the following
to your Cargo.toml
:
[dependencies]
rustyline = "15.0.0"
Features
- Unicode (UTF-8) (linenoise supports only ASCII)
- Word completion (linenoise supports only line completion)
- Filename completion
- History search (Searching for Commands in the History)
- Kill ring (Killing Commands)
- Multi line support (line wrapping)
- Word commands
- Hints
Actions
For all modes:
Keystroke | Action |
---|---|
Home | Move cursor to the beginning of line |
End | Move cursor to end of line |
Left | Move cursor one character left |
Right | Move cursor one character right |
Ctrl-C | Interrupt/Cancel edition |
Ctrl-D, Del | (if line is not empty) Delete character under cursor |
Ctrl-D | (if line is empty) End of File |
Ctrl-J, Ctrl-M, Enter | Finish the line entry |
Ctrl-R | Reverse Search history (Ctrl-S forward, Ctrl-G cancel) |
Ctrl-T | Transpose previous character with current character |
Ctrl-U | Delete from start of line to cursor |
Ctrl-V | Insert any special character without performing its associated action (#65) |
Ctrl-W | Delete word leading up to cursor (using white space as a word boundary) |
Ctrl-Y | Paste from Yank buffer |
Ctrl-Z | Suspend (Unix only) |
Ctrl-_ | Undo |
Emacs mode (default mode)
Keystroke | Action |
---|---|
Ctrl-A, Home | Move cursor to the beginning of line |
Ctrl-B, Left | Move cursor one character left |
Ctrl-E, End | Move cursor to end of line |
Ctrl-F, Right | Move cursor one character right |
Ctrl-H, Backspace | Delete character before cursor |
Ctrl-I, Tab | Next completion |
Ctrl-K | Delete from cursor to end of line |
Ctrl-L | Clear screen |
Ctrl-N, Down | Next match from history |
Ctrl-P, Up | Previous match from history |
Ctrl-X Ctrl-U | Undo |
Ctrl-Y | Paste from Yank buffer (Meta-Y to paste next yank instead) |
Meta-< | Move to first entry in history |
Meta-> | Move to last entry in history |
Meta-B, Alt-Left | Move cursor to previous word |
Meta-C | Capitalize the current word |
Meta-D | Delete forwards one word |
Meta-F, Alt-Right | Move cursor to next word |
Meta-L | Lower-case the next word |
Meta-T | Transpose words |
Meta-U | Upper-case the next word |
Meta-Y | See Ctrl-Y |
Meta-Backspace | Kill from the start of the current word, or, if between words, to the start of the previous word |
Meta-0, 1, ..., - | Specify the digit to the argument. â starts a negative argument. |
Readline Emacs Editing Mode Cheat Sheet
vi command mode
Keystroke | Action |
---|---|
$, End | Move cursor to end of line |
. | Redo the last text modification |
; | Redo the last character finding command |
, | Redo the last character finding command in opposite direction |
0, Home | Move cursor to the beginning of line |
^ | Move to the first non-blank character of line |
a | Insert after cursor |
A | Insert at the end of line |
b | Move one word or token left |
B | Move one non-blank word left |
c | Change text of a movement command |
C | Change text to the end of line (equivalent to c$) |
d | Delete text of a movement command |
D, Ctrl-K | Delete to the end of the line |
e | Move to the end of the current word |
E | Move to the end of the current non-blank word |
f | Move right to the next occurrence of char |
F | Move left to the previous occurrence of char |
h, Ctrl-H, Backspace | Move one character left |
l, Space | Move one character right |
Ctrl-L | Clear screen |
i | Insert before cursor |
I | Insert at the beginning of line |
+, j, Ctrl-N | Move forward one command in history |
-, k, Ctrl-P | Move backward one command in history |
p | Insert the yanked text at the cursor (paste) |
P | Insert the yanked text before the cursor |
r | Replaces a single character under the cursor (without leaving command mode) |
s | Delete a single character under the cursor and enter input mode |
S | Change current line (equivalent to 0c$) |
t | Move right to the next occurrence of char , then one char backward |
T | Move left to the previous occurrence of char , then one char forward |
u | Undo |
w | Move one word or token right |
W | Move one non-blank word right |
x | Delete a single character under the cursor |
X | Delete a character before the cursor |
y | Yank a movement into buffer (copy) |
vi insert mode
Keystroke | Action |
---|---|
Ctrl-H, Backspace | Delete character before cursor |
Ctrl-I, Tab | Next completion |
Esc | Switch to command mode |
Readline vi Editing Mode Cheat Sheet
Wine
$ cargo run --example example --target 'x86_64-pc-windows-gnu'
...
Error: Io(Error { repr: Os { code: 6, message: "Invalid handle." } })
$ wineconsole --backend=curses target/x86_64-pc-windows-gnu/debug/examples/example.exe
...
Terminal checks
$ # current settings of all terminal attributes:
$ stty -a
$ # key bindings:
$ bind -p
$ # print out a terminfo description:
$ infocmp
Similar projects
Library | Lang | OS | Term | Unicode | History | Completion | Keymap | Kill Ring | Undo | Colors | Hint/Auto suggest |
---|---|---|---|---|---|---|---|---|---|---|---|
go-prompt | Go | Ux/win | ANSI | Yes | Yes | any | Emacs/prog | No | No | Yes | Yes |
Haskeline | Haskell | Ux/Win | Any | Yes | Yes | any | Emacs/vi/conf | Yes | Yes | ? | ? |
isocline | C | Ux/Win | ANSI | Yes | Yes | any | Emacs | No | Yes | Yes | Yes |
linefeed | Rust | Ux/Win | Any | Yes | any | Emacs/conf | Yes | No | ? | No | |
linenoise | C | Ux | ANSI | No | Yes | only line | Emacs | No | No | Ux | Yes |
Liner | Rust | Ux | ANSI | No inc search | only word | Emacs/vi/prog | No | Yes | Ux | History based | |
prompt_toolkit | Python | Ux/Win | ANSI | Yes | Yes | any | Emacs/vi/conf | Yes | Yes | Ux/Win | Yes |
reedline | Rust | Ux/Win | ANSI | Yes | Yes | any | Emacs/vi/bind | No | Yes | Ux/Win | Yes |
replxx | C/C++ | Ux/Win | ANSI | Yes | Yes | only line | Emacs | Yes | No | Ux/Win | Yes |
Rustyline | Rust | Ux/Win | ANSI | Yes | Yes | any | Emacs/vi/bind | Yes | Yes | Ux/Win 10+ | Yes |
termwiz | Rust | Ux/Win | Any | ? | Yes | any | Emacs | No | No | Ux/Win | No |
Multi line support
This is a very simple feature that simply causes lines that are longer than the current terminal width to be displayed on the next visual line instead of horizontally scrolling as more characters are typed. Currently, this feature is always enabled and there is no configuration option to disable it.
This feature does not allow the end user to hit a special key sequence and enter a mode where hitting the return key will cause a literal newline to be added to the input buffer.
The way to achieve multi-line editing is to implement the Validator
trait.
Minimum supported Rust version (MSRV)
Latest stable Rust version at the time of release. It might compile with older versions.
Top Related Projects
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot