On Wed, Mar 22, 2017 at 01:59:43PM +0200, Pekka Paalanen wrote:
> On Wed, 22 Mar 2017 12:23:46 +1000
> Peter Hutterer wrote:
>
> > Hi all,
> >
> > This is an RFC for a new interface to generate input events from arbitrary
> > clients. Note that this is only a few days
On Thursday, 2017-03-23 11:59:22 -0500, Derek Foreman wrote:
> posix_fallocate() can return EINTR and need to be restarted - I've hit
> this when running weston-terminal under gdb.
>
> Signed-off-by: Derek Foreman
Both patches are:
Reviewed-by: Eric Engestrom
posix_fallocate() can return EINTR and need to be restarted - I've hit
this when running weston-terminal under gdb.
Signed-off-by: Derek Foreman
---
shared/os-compatibility.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/shared/os-compatibility.c
The man page indicates that ftruncate() can set errno to EINTR, so test
for this.
I have not actually been able to provoke an EINTR error from ftruncate()
in testing though.
Signed-off-by: Derek Foreman
---
shared/os-compatibility.c | 4 +++-
1 file changed, 3
Hi,
On 22 March 2017 at 14:35, Pekka Paalanen wrote:
> On Fri, 3 Mar 2017 23:05:25 +
> Daniel Stone wrote:
>> Clean up some ambiguity around current/next: current could previously
>> have referred to a buffer which was being displayed, or the
Hi,
> I can't imagine blocking all/none shortcuts can be the only choices.
> What if the nested wm does not use one of the shortcuts? And whether a
> particular shortcut is used can vary: a tab between windows may not
> work if you are on the last window, in that case it would be nice if
> tab