Christophe-Marie Duquesne

> I'm good with installing this by default, but if we do we probably should stop installing the other triggers by default?! Right, I can deactivate them in the Makefile...

Ok, after toying around, I understand that the Makefile is not the right place to do that. I guess what we want is to change the default targets in `contrib/packaging`?...

@phillipberndt As a user, I would have expected autorandr to treat lid open/close events as a screen connect/disconnect. At least this is essentially how I think about it when I...

> This change would increase the complexity from a user's perspective a lot. Honestly, after going through this, I would find it easier if autorandr treated a closed lid as...

> Does every notebook expose lid state through /proc/acpi/button/lid/LID0/state? (I guess the answer to that is yes) For some laptops, the lid state appears to be reported in `/proc/acpi/button/lid/LID/state` (see...

Hi, I developed a branch where a closed lid is treated as if it was a disconnected output. This means, essentially, that running `autorandr --save` while the lid is closed...

1. Good idea, I will count the number of screens. 2. Ok, I will add command line options to override lid output name and lid state file. 3. I disagree...

**1** is now implemented. I elected not to implement **2**, because I believe that my version covers all cases (as I mentioned in the PR, I went through the code...

Cool, thanks! As far as I am concerned, this issue can be closed, then 🙂

Note for whoever wants to turn this suggestion into an implementation: https://wiki.python.org/moin/DbusExamples recommends [pydbus](https://github.com/LEW21/pydbus) as a modern dbus library.