On Wed, Feb 16, 2022 at 05:39:14PM +0100, Hiltjo Posthuma wrote: > whats the solution/patch?
If there is a "standard" (or at least conventional) way of communicating the active monitor between wm and other X clients then it's probably best to follow that. Assuming there isn't, one alternative could be just using env vars. dwm would set an env var, say $DWM_CURRENT_MONITOR inside spawn() and `dmenu_run` can be adjusted to utilize that `-m "$DWM_CURRENT_MONITOR"` or fallback to some default if the env var doesn't exist. This would remove the need to special case dmenucmd and would allow other scripts/programs spawned via dwm to utilize this env var as well. On Wed, Feb 16, 2022 at 05:39:14PM +0100, Hiltjo Posthuma wrote: > Whats the issue Wouldn't consider it an "issue", but rather a place for potential improvement. - NRK
