rlwrap VS wsl-ssh-pageant

Possibly more universal, but there are also tools like rlwrap [1] that adds readline support to programs that don't have it. From the docs apparently the readline library ships a similar tool ootb nowadays but I haven't tried that and just noticed now when I wanted to share the rlwrap link.

[1] https://github.com/hanslub42/rlwrap

Otherwise I use rlwrap, which is a general purpose readline wrapper: https://github.com/hanslub42/rlwrap It's pretty basic stuff, but makes basic line editing less painful, & adds history support.

Friends if you dont know: you can add readline support to LOTS of things, especially custom scripts and tools with a prompt by just calling the program with rlwrap.

> rlwrap is a 'readline wrapper', a small utility that uses the GNU Readline library to allow the editing of keyboard input for any command.

https://github.com/hanslub42/rlwrap

rlwrap for any interactive command will give it a history. You can even build a file to have tab completion. https://github.com/hanslub42/rlwrap

rlwrap is a 'readline wrapper', a small utility that uses the GNU Readline library to allow the editing of keyboard input for any command, something that tclsh, wish and sbcl don't provide.

This can be as easy as wrapping a simple stdin/stdout loop with rlwrap, all the way to using full featured TUI libraries like bubbletea (golang), textual (python) or imtui (c++).

You could always use rlwrap (installable via homebrew). You would launch R with rlwrap R in that case. However, I suspect there is something else missing, because it appears that the R repl usually includes readline support. Thus my questions about installation method and OS.

As you can see ,clj, behind the scenes, wraps a call to $bin_dir/clojure with the rlwrap tool. rlwrap provides a better command-line editing experience.

If read-line functionality is missing from languages that provide repls or command line interpreters, rlwrap has always served me well on linux. Many distros provide their own package too.

I have written these sorts of things, but I do try and put them up on GitHub if I think they’ll be useful to other people. I wrote a tool unimaginatively named wsl-ssh-pageant [0] which I wanted because I use a YubiKey for my SSH key but wanted it to be available in WSL. It has been by far my most popular GitHub project.

I do have other things as well, some on GitHub some not. A scraper to notify me when a local gym booking website changes for a time I’m interested in. A bridge between a BroadLink RM4 and HomeKit for some fans [1] - I wanted to avoid home-assistant. A script to grab my power consumption data. A shim to make gpg-agent compatible with launchd’s socket activation protocol [2].

[0] - https://github.com/benpye/wsl-ssh-pageant

[1] - https://github.com/benpye/hkrm4

[2] - https://github.com/benpye/launchd_shim

I don't need to pass a path to the gpg socket to wsl-ssh-pageant. I just pass it the UNC path for the socket I want it to open.

In the past I also used https://github.com/benpye/wsl-ssh-pageant to go from WSL to Pageant (which I believe KeeAgent is also compatible with)