projects / redis.git / blame
| Commit | Line | Data |
|---|---|---|
| e902b579 PN |
1 | # Linenoise |
| 2 | ||
| 3 | A minimal, zero-config, BSD licensed, readline replacement. | |
| 4 | ||
| 5 | News: linenoise is now part of [Android](http://android.git.kernel.org/?p=platform/system/core.git;a=tree;f=liblinenoise;h=56450eaed7f783760e5e6a5993ef75cde2e29dea;hb=HEAD Android)! | |
| 6 | ||
| 7 | ## Can a line editing library be 20k lines of code? | |
| 8 | ||
| 9 | Line editing with some support for history is a really important feature for command line utilities. Instead of retyping almost the same stuff again and again it's just much better to hit the up arrow and edit on syntax errors, or in order to try a slightly different command. But apparently code dealing with terminals is some sort of Black Magic: readline is 30k lines of code, libedit 20k. Is it reasonable to link small utilities to huge libraries just to get a minimal support for line editing? | |
| 10 | ||
| 11 | So what usually happens is either: | |
| 12 | ||
| 13 | * Large programs with configure scripts disabling line editing if readline is not present in the system, or not supporting it at all since readline is GPL licensed and libedit (the BSD clone) is not as known and available as readline is (Readl world example of this problem: Tclsh). | |
| 14 | * Smaller programs not using a configure script not supporting line editing at all (A problem we had with Redis-cli for instance). | |
| 15 | ||
| 16 | The result is a pollution of binaries without line editing support. | |
| 17 | ||
| 18 | So I spent more or less two hours doing a reality check resulting in this little library: is it *really* needed for a line editing library to be 20k lines of code? Apparently not, it is possibe to get a very small, zero configuration, trivial to embed library, that solves the problem. Smaller programs will just include this, supporing line editing out of the box. Larger programs may use this little library or just checking with configure if readline/libedit is available and resorting to linenoise if not. | |
| 19 | ||
| 20 | ## Terminals, in 2010. | |
| 21 | ||
| 22 | Apparently almost every terminal you can happen to use today has some kind of support for VT100 alike escape sequences. So I tried to write a lib using just very basic VT100 features. The resulting library appears to work everywhere I tried to use it. | |
| 23 | ||
| 24 | Since it's so young I guess there are a few bugs, or the lib may not compile or work with some operating system, but it's a matter of a few weeks and eventually we'll get it right, and there will be no excuses for not shipping command line tools without built-in line editing support. | |
| 25 | ||
| 26 | The library is currently less than 400 lines of code. In order to use it in your project just look at the *example.c* file in the source distribution, it is trivial. Linenoise is BSD code, so you can use both in free software and commercial software. | |
| 27 | ||
| 28 | ## Tested with... | |
| 29 | ||
| 30 | * Linux text only console ($TERM = linux) | |
| 31 | * Linux KDE terminal application ($TERM = xterm) | |
| 32 | * Linux xterm ($TERM = xterm) | |
| 33 | * Mac OS X iTerm ($TERM = xterm) | |
| 34 | * Mac OS X default Terminal.app ($TERM = xterm) | |
| 35 | * OpenBSD 4.5 through an OSX Terminal.app ($TERM = screen) | |
| 36 | * IBM AIX 6.1 | |
| 37 | * FreeBSD xterm ($TERM = xterm) | |
| 38 | ||
| 39 | Please test it everywhere you can and report back! | |
| 40 | ||
| 41 | ## Let's push this forward! | |
| 42 | ||
| 43 | Please fork it and add something interesting and send me a pull request. What's especially interesting are fixes, new key bindings, completion. | |
| 44 | ||
| 45 | Send feedbacks to antirez at gmail |