4 ms·
Ha, same here, actually. There is an older stand-alone Unix port as well, though -- this is what I built and use (sam -d), because I don't need the entire p9p e
by marttt 4y ago
Ha, same here, actually. There is an older stand-alone Unix
port as well, though -- this is what I built and use (sam -d),
because I don't need the entire p9p ecosystem.
I actually use it with rlwrap to get line editing history:
rlwrap -n sam -d $@
I really like sam's command language, it is mildly addictive.
Apparently, a stand-alone Unix sam is also available in 9base:
http://tools.suckless.org/9base http://tools.suckless.org/9base
- 1vuio0pswjnm7 4y agoTo get readline, I use socat instead of rlwrap. The later feels more sluggish. I learned about the sam port with the -d option from you, so thanks for that.
- marttt 4y agoYes, I remember testing socat as well for that purpose, and it worked great. Since I didn't have much other use for it at that point, I still went with rlwrap in the end. I imagine you can really do a lot with socat, though. An impressive tool. As for sam, the 9front version has a few additions (_ and ^) that make it quicker to manipulate the selected range with commands in sam's language that are stored in an external file [1]. Too bad this isn't included out of the box in the Unix versions. When one is using sam -d, this would give a more streamlined workflow for more complex editing tasks (no need to write external scripts in another language, sed, awk, etc). There was a 9front sam port for Unix somewhere as well, though, but I haven't tried to build it. 1: http://man.9front.org/1/sam http://man.9front.org/1/sam