You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since readline won't work an alternative needs to be found. A pure Go library would be ideal. But decent C bindings with a reasonable license would be fine too. This thread should collect requirements and decide on an alternative package.
Left/Right arrow key support is the absolute minimum of what's needed.
History support (built in or hackable).
Auto complete support (built in or hackable). This could have varying degrees of awesomeness. Any would probably be preferable over none.
Reverse i-search support (built in or hackable).
Things like my vim ~/.inputrc bindings are probably a lot cause (nooooo!).
The text was updated successfully, but these errors were encountered:
bmatsuo
changed the title
readline (or equivalent)
readline (or alternative)
Jun 30, 2014
If someone wanted to help all they need to do is rewrite, or provide a new implementation of, the ShellReader interface which parses commands into string slices. It's pretty straight forward.
Ping me @bmatsuo before you start working on this so I can agree beforehand to the library you want to use and your plan.
For now rlwrap seems to do a sufficient job with the proper options.
rlwrap -A -N jqsh
The rlwrap man page suggests that -N is Linux only (edit: a warning is also displayed on startup), but it seemed to help for me on OS X 10.9 Mavericks. /shrug
I don't think readline proper is the right way to go. The utility needs to be statically linked IMO. That would mean including the readline source and making the license GNU GPL.
Since readline won't work an alternative needs to be found. A pure Go library would be ideal. But decent C bindings with a reasonable license would be fine too. This thread should collect requirements and decide on an alternative package.
Things like my vim
~/.inputrc
bindings are probably a lot cause (nooooo!).The text was updated successfully, but these errors were encountered: