On Wed, Oct 31, 2018 at 06:53:00PM +0100 I heard the voice of Rhialto, and lo! it spake thus: > > But I am now left wondering if we can improve on this somehow. My > thoughts have ranged from making key bindings somehow depending on > the screen they are in (and then there must be some pre-defined m4 > macros for the screen layout so we can define the keys for each > screen context appropriately), to extending the "script" language > with calculations or even importing some existing script interpreter > for the job.
Yeah. And what does "screen you're on" mean? e.g., for things like f.fullscreenzoom, the rlayout code has to figure out out which screen to full_zoom on when a window is spanning several. It chooses the screen that has the largest area of the window on it, but if your pointer were in the win on a a different screen from that when you ran <whatever> func, which screen should that be considered acting on? We could definitely fall down an eternal rabbit hole of adding more special-purpose f.'s that never really solved the problem, just built up an unmaintainable monstrosity. Certainly the sort of things that fits better with the ability to built arbitrary scripting capability into things. It's a thing I mentally toy with from time to time, but it's a biiiiiig job to retrofit... -- Matthew Fuller (MF4839) | [email protected] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
