Jan Pokorný

On 17/11/16 12:15 +0100, Jan Pokorný wrote: > Being string on fsid would alleviate this issue, of new approach is > to be chosen. s/string/strict/ :-) ## Jan (Poki)

Please see #887 if you find it any better. It's still somewhat bound to lazy side of the scale, but is a bit more systemic, IMHO.

On 21/11/16 08:13 -0800, Dejan Muhamedagic wrote: > What I've been trying to understand is the motivation for the > change: can someone shed some light on that aspect. If...

On 23/11/16 05:06 -0800, Dejan Muhamedagic wrote: > On Tue, Nov 22, 2016 at 08:15:10AM -0800, Jan Pokorný wrote: >> On 21/11/16 08:13 -0800, Dejan Muhamedagic wrote: >>> What I've...

On 24/11/16 20:59 +0100, Jan Pokorný wrote: > On 23/11/16 05:06 -0800, Dejan Muhamedagic wrote: >> If I had to read exportfs(8) and you had to prowl the nfs-utils >>...

On 30/11/16 05:33 -0800, Dejan Muhamedagic wrote: > If an "unauthorized admin" has gained control of the CIB, then > the game's long over; what happens with the fsid parameter...

Would any sort of driver-agnostic workaround be thinkable for the case of edges being cut off? Something like: ``` output 'Troubling monitor' resolution 1920x1080@60Hz \ blindfold_padding 30 50 30 50...

Discovered there is `gaps` property of the workspace already, with all the per-edge separate configurability. So I'd likely be able to have something sufficient if I configured/scripted workspace-to-output assignment and...

Note that with this alleged misbehaviour, problems keep chaining in hard to anticipate ways! For instance, for my terminal purposes, I am using urxvt256c-mld for which I've written a user...

Note that Travis CI runs are currently borked. There must have been a change on their side that is causing this, I can't even successfully finish what was once passing:...