Hi,
I think it's a typo in the cheat sheet; at least for s///,
\i is the correct syntax to reference "tagged patterns":
% echo foo bar | ssam 's/([a-z]+) ([a-z]+)/\2 \1/'
bar foo
I lack familiarity with sam/sam's language to be certain,
but I doubt it'd make much sense to have it for other
c
1/ opening the event file disables menu management. one can
write 'menu' to ctl (should still be undocumented) to re-enable it.
2/ xfideventwrite() (src/cmd/acme/xfid.c) doesn't seem to handle
"keyboard insert" events (e.g. "KI275 275 0 1 e"; third integers
is a flag; acme(4) only describes writin
I often consider acme as being a "clumsily programmable set
of text windows". I've often wondered about simplifying it as such.
e.g. replacing 9P by an ~RPC interface (+ an event stream?),
giving a simple, complete programmatic control over the editor.
usual commands (Undo, Snarf, etc.) would all
