On 4/2/25 01:41, Mathieu Bivert wrote:
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 writing event with a flag to 1).
one can still insert text using the addr/data files, e.g. simulating
the previous "KI" event with:
$ echo -n '#275' | 9p write acme/796/addr # or '#275,#275'
$ echo -n e | 9p write acme/796/data
3/ in my experience, at least on UNIX, something like sxhkd[0] has
been preferable to acme events for shortcuts, albeit imperfect. in
particular, I remember frequently hitting a race or something
(iirc in 9pserve) when registering an "event handler" (reading
acme event files) on all buffers.
hope it helps,
[0]: https://github.com/baskerville/sxhkd <https://github.com/
baskerville/sxhkd>
Wow, thank you, that is exactly what I needed. I'm not so much
interested in writing random text, but mapping Ctrl-key shortcuts and I
hope sxhkd can do that !
------------------------------------------
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T08b139f442c68dca-M92050f400557e42386552ecf
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
