Re: [PATCH libinput] test: call K_OFF when run on the vt

On Thu, Apr 05, 2018 at 12:53:45PM +0300, Pekka Paalanen wrote: > On Thu, 5 Apr 2018 15:18:08 +1000 > Peter Hutterer wrote: > > > Slight disadvantage: this breaks Ctrl+C to cancel the test suite when run > > from the VT. Still potentially better than injecting

Re: [PATCH libinput 0/1] Initialization race against udev

On Thu, Apr 05, 2018 at 01:20:51PM +, Friedrich, Eugen (ADITG/ESB) wrote: > Hi Peter > > Best regards > > Eugen Friedrich > Engineering Software Base (ADITG/ESB) > > Tel. +49 5121 49 6921 > > > -Original Message- > > From: wayland-devel [mailto:wayland-devel- > >

Re: [PATCH weston 10/25] man: document WESTON_LIBINPUT_LOG_PRIORITY env

On Thu, Apr 05, 2018 at 04:53:53PM +0300, Pekka Paalanen wrote: > On Thu, 5 Apr 2018 15:59:18 +1000 > Peter Hutterer wrote: > > > On Fri, Mar 23, 2018 at 02:00:50PM +0200, Pekka Paalanen wrote: > > > From: Pekka Paalanen > > > > > >

Re: [PATCH] terminal: Fix unintended fallthrough to cursor restore

On 2018-04-03 01:38 PM, Daniel Stone wrote: > ef57a9b788 added support for window operations such as reporting the > title in escape mode. It implemented this by which-window-op case, > inside the existing which-escape-code case. Whilst it would break out of > the former window-op case, it never

Re: [PATCH weston 09/25] libinput: do not switch output associations on disable

On Thu, 5 Apr 2018 16:10:53 +1000 Peter Hutterer wrote: > On Fri, Mar 23, 2018 at 02:00:49PM +0200, Pekka Paalanen wrote: > > From: Pekka Paalanen > > > > If an input device is associated to an output that then gets disabled, > > there

Re: [PATCH weston 10/25] man: document WESTON_LIBINPUT_LOG_PRIORITY env

On Thu, 5 Apr 2018 15:59:18 +1000 Peter Hutterer wrote: > On Fri, Mar 23, 2018 at 02:00:50PM +0200, Pekka Paalanen wrote: > > From: Pekka Paalanen > > > > Commit c81c4241d9c9fc5f60c08177dd8a33ae4e4ddca1 added this environment > >

Re: [PATCH libinput 0/1] Initialization race against udev

On Thu, 5 Apr 2018 13:20:51 + "Friedrich, Eugen (ADITG/ESB)" wrote: > Hi Peter > > Best regards > > Eugen Friedrich > Engineering Software Base (ADITG/ESB) > > Tel. +49 5121 49 6921 > > > -Original Message- > > From: wayland-devel [mailto:wayland-devel-

RE: [PATCH libinput 0/1] Initialization race against udev

Hi Peter Best regards Eugen Friedrich Engineering Software Base (ADITG/ESB) Tel. +49 5121 49 6921 > -Original Message- > From: wayland-devel [mailto:wayland-devel- > boun...@lists.freedesktop.org] On Behalf Of Peter Hutterer > Sent: Donnerstag, 5. April 2018 06:27 > To: Matt Hoosier >

Re: [PATCH libinput] test: call K_OFF when run on the vt

On Thu, 5 Apr 2018 15:18:08 +1000 Peter Hutterer wrote: > Slight disadvantage: this breaks Ctrl+C to cancel the test suite when run > from the VT. Still potentially better than injecting semi-random events. > > Signed-off-by: Peter Hutterer >

Re: Where's the documentation for weston and libweston?

* Hello, I would prefer if you kept all discussion public, on the mailing list or #wayland IRC channel in Freenode, if possible, as I cannot really do private guidance for everyone. As for learning, I suppose you can follow what's going on in IRC and the mailing list, look at

Re: Where's the documentation for weston and libweston?

On Thu, 5 Apr 2018 12:15:22 +0530 Saga _-_ wrote: > `make doc` in the weston github repo build documentation only for some > unit test tool `zunitc`. The wayland documentation at > https://wayland.freedesktop.org/docs/html/ doesn't mention weston > anywhere. Where can I find

Re: [PATCH weston 11/25] tests: add test_seat_release() for symmetry

On Fri, Mar 23, 2018 at 02:00:51PM +0200, Pekka Paalanen wrote: > From: Pekka Paalanen > > Add test_seat_release() as the counterpart of test_seat_init() instead > of open-coding it. This helps adding more code to test_seat_release() > later. > > Signed-off-by:

Re: [PATCH weston 09/25] libinput: do not switch output associations on disable

On Fri, Mar 23, 2018 at 02:00:49PM +0200, Pekka Paalanen wrote: > From: Pekka Paalanen > > If an input device is associated to an output that then gets disabled, > there is no case where associating to a different output would be > correct. just a general note