This is interesting, but I'm curious: what do people think are the advantages or disadvantages of using this instead of Ruby's own readline support?
(My first thought: rlwrap already exists. Add one point. A disadvantage is that rlwrap makes the readline support depend on an external, third-party program which would need to be installed separately. Subtract one?)
I agree. Minimizing external dependencies (with a particular focus on the OS X experience) was a guiding principle of the project.
I will probably use Ruby Readline (http://bogojoker.com/readline) to implement this. Another planned feature will likely require using Curses. It would be nice to reduce these two dependencies to one, but I'm not sure I'll start by reimplementing Ruby Readline in Curses.
Comments
rlwrap http://utopia.knoware.nl/~hlub/uck/rlwrap/
This is interesting, but I'm curious: what do people think are the advantages or disadvantages of using this instead of Ruby's own readline support?
(My first thought: rlwrap already exists. Add one point. A disadvantage is that rlwrap makes the readline support depend on an external, third-party program which would need to be installed separately. Subtract one?)
I agree. Minimizing external dependencies (with a particular focus on the OS X experience) was a guiding principle of the project.
I will probably use Ruby Readline (http://bogojoker.com/readline) to implement this. Another planned feature will likely require using Curses. It would be nice to reduce these two dependencies to one, but I'm not sure I'll start by reimplementing Ruby Readline in Curses.
rlwrap is useful, but it lacks command tab completion.
Typing
http://www.google.com>; co[tab]-a
is much easier than typing
http://www.google.com>; cookies-a
rlwrap can do completion, given a little setting-up: http://utopia.knoware.nl/~hlub/rlwrap/rlwrap.html