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
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
Sorry I wasn't really clear, I'm talking about, in your example,
`acme/29/event`. acme(4) explains I can also receive keyboard events and I do,
I can get the characters I enter, but sending them back in has the behaviour I
explained. I'm using `wineventloop` from acme.rc, and my event function i
You said "acme's event files on windows". To be absolutely precise: you
mean this kind of window (from p9p and Edwood) (the 29 in this context)?
; 9p ls acme/29
addr
body
ctl
data
editout
errors
event
rdsel
tag
wrsel
xdata
So: what's the exact command line with args that you're running? Because
t
Has anyone managed to do anything productive with acme's event files on
windows and the keyboard ? All I can find is mouse-related scripts.
I'm trying to do keybindings the easy way, by tapping into that event
file, but I have some issues:
- When text is added the tag isn't updated with Und
Has anyone managed to do anything productive with acme's event files on
windows and the keyboard ? All I can find is mouse-related scripts.
I'm trying to do keybindings the easy way, by tapping into that event
file, but I have some issues:
- When text is added the tag isn't updated with Undo
