Christopher Hoage

> i suspect it may be libconfig’s issue rather than picom’s. thank you for additional information. That makes sense! If it turns out to be an issue with that library,...

Thank you for the investigation! > i've read commit description and for me old behavior wasn't really confusing I happen to agree. When a file is symlinked and read from...

@yshui Do you have any thoughts on the above investigation and possibly reverting https://github.com/yshui/picom/commit/a8b15f3a1b9111d0e0facd0ea413e8566a9d0a58?

This is still problematic for me - wondering if there may be other solutions to be considered? One idea I had was to allow `picom --include-dir=$HOME/.config/picom` That should allow the...

Yes, that would work - the important thing to me is I can symlink files into a known location and read those symlinks with out a fully qualified path. E.g....

Yes, it would. I could symlink `common.conf` to the include dir and preserve my system specific `picom.conf` files.

> I have the same C920. Had the exact same issue. Changing focus_auto = 0 to focus_automatic_continuous = 0 solved it for me. For anyone coming from google this may...

For me it is around the simplicity of exposing - and by extension securing - publicly accessible services. I find the cognitive load of securing a single (sub)domain via some...

No problem I'll keep an eye on this issue to see. Thank you!

So I noticed I had some user error in my original example `getLibraryItems` appears to require two parameters, and I was only supplying one in my example code above. However...