You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In that window, 2-1 chord some arguments to some command, say a path to ls.
Notice that winwriteevent dropped the chorded arguments.
The same thing happens for Win.WriteEvent from the 9fans.net/go/acme Go package.
The acmeevent(1) man page states:
Only the first four arguments are necessary: the rest are ignored.
but it doesn’t seem to be the case that only those are necessary, and this makes it impossible to use chording in Acme clients on commands that the clients don’t handle themselves.
Or maybe I’m misunderstanding, in which case maybe we could improve the docs?
The text was updated successfully, but these errors were encountered:
Write a script that reads acme events and passes them through to Acme:
Run that script in an Acme window.
In that window, 2-1 chord some arguments to some command, say a path to
ls
.Notice that
winwriteevent
dropped the chorded arguments.The same thing happens for Win.WriteEvent from the 9fans.net/go/acme Go package.
The acmeevent(1) man page states:
but it doesn’t seem to be the case that only those are necessary, and this makes it impossible to use chording in Acme clients on commands that the clients don’t handle themselves.
Or maybe I’m misunderstanding, in which case maybe we could improve the docs?
The text was updated successfully, but these errors were encountered: