hi, in order to attempt an implementation of getpidforcommand for other systems, it would be really useful for me to know how can its results be observed ;)
so, given a pid, it will reconstruct the process' argv and argc, which is used (src/window.c:fixLeaderProperties(), using XSetCommand(); called from wManageWindow()) to set a client's WM_COMMAND property, in some cases(?). when are there practical implications of this, what are they, and how can they be observed? i'm also running wm on a netbsd now, for which there certainly isn't a getcommandforpid() (i have unmounted /proc on it), yet xprop shows a correct WM_COMMAND string array. i suspect (*fix*LeaderProperties seems a giveaway) that is a kludge for some clients that do not do something that a well-behaving client does, and i just couldn't quickly find any. is that assessment about right? anyone knows an app affected by this? or any other way to know when is it kicking in, possibly with a way of deliberately triggering it? thanks, -- [-] mkdir /nonexistent -- To unsubscribe, send mail to [email protected].
