Hi Brian, Sorry for the small response delay. ;) This is my only Debian package and I have let things go for a while now. I'm trying to get back on this.
> Maybe. However it is probably not a bug in xss-lock... How would you > phrase such a question? I'm not sure. :D According to the upstream's README file, they're supposed to "pick" the changes from master to the `dualmonitor` branch (see [1]), so I think that you should try to propose the change there at least, i.e. make a pull request onto the `dualbranch` over the upsteam repository. However, since this change is really deal breaker for you (and some others using xss-lock) and since upstream doesn't do much to advance development of the `dualmonitor` branch, then I think that we should include your patch in the meantime. I have tested it and it works nicely for me. The only thing bothering me is that it takes one additional second to spawn the script (I tested with `time` multiple times on both versions). Anyway, that's not too bad, I guess. I'll upload the change shortly and close this issue. [1]: https://github.com/meskarune/i3lock-fancy#multiple-monitors Le lun. 10 sept. 2018, à 18 h 12, Brian May <b...@debian.org> a écrit : > Simon Désaulniers <sim.desaulni...@gmail.com> writes: > > > Noted. May be that would be worth to formulate as a question to > xss-lock's > > upstream too? > > Maybe. However it is probably not a bug in xss-lock... How would you > phrase such a question? > -- > Brian May <b...@debian.org> >
Le lun. 10 sept. 2018, à 18 h 12, Brian May <b...@debian.org> a écrit :
Simon Désaulniers <sim.desaulni...@gmail.com> writes:
> Noted. May be that would be worth to formulate as a question to xss-lock's
> upstream too?
Maybe. However it is probably not a bug in xss-lock... How would you
phrase such a question?
--
Brian May <b...@debian.org>
signature.asc
Description: PGP signature
