acme: no path logged in acme/log for new win windows
mye opened this issue · 0 comments
mye commented
win writes the process name prefixed with "-" to the acme ctl file, but that information doesn't appear in 9p read acme/log, new windows only get their id and a new event, as opposed to real files where the path is also there.
This prevents me from reacting to win windows when tailing acme/log because I can't match on the (process) names.
I believe xfidlog could be called when the window path is set, not when a new (anonymous) window is made and the path isn't known yet?