Martin Hradil

(https://github.com/Bttstrp/bootstrap-switch/issues/707 and https://github.com/Bttstrp/bootstrap-switch/issues/709 are dups of this issue, referencing)

It appears 3.3.5 and 3.4.0 were not made by @LostCrew, or at least not committed to this repository. Reporting to npm.

@LostCrew nope, I have not received any reply in that email thread. Which probably means that npm hasn't received it either, please try again, and use Reply All? (If you...

Anyone working on this? I could use this feature so I'm willing to take it :)

:+1: for a simple map, I use aliases to anchor local imports to the module root, so you don't have to think about `../components` vs `../../components`. (Webpack: `resolve.alias = {...

:+1:, though I only really want it to comment when tests fail (and clean up once they succeed again).

Seeing the same thing, unfortunately this seems to be an imlib2 issue... ``` imlib_image_fill_color_range_rectangle(1000, 1000, 4096, 1000, 0); ``` renders a perfectly valid gradient, but ``` imlib_image_fill_color_range_rectangle(1000, 1000, 4097, 1000,...

Aah, finally, I knew there must be somebody still using X screens :). Your propsal sounds reasonable, just one question: Right now, not using `-screens` (or `-screen`) gives you screen...

Thanks! And you're right, maybe just a `-screen ` would be the best. (Though, I still feel like maybe `DISPLAY=:1.0` should just touch screen 0, whereas `DISPLAY=:1` should touch all...

I think you may be seeing the same as #42 .. that is, gradient DOES work with root .. unless the total root window size is more than 4096 in...