Re: [PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

Em 9 de fev de 2016 05:49, "Peter Hutterer" escreveu: > > On Tue, Feb 09, 2016 at 05:40:26AM -0200, Laércio de Sousa wrote: > > Em 9 de fev de 2016 02:24, "Peter Hutterer" > > escreveu: > > > > > > On Fri, Dec 11, 2015 at 11:43:10AM -0200,

Re: [PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

Em 9 de fev de 2016 02:24, "Peter Hutterer" escreveu: > when we introduced the udev config backend we mostly agreed that we weren't > going to use udev as a config storage (which is how InputClass was > conceived). Debian ships them because there was some release timing

Re: [PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

On Tue, Feb 9, 2016 at 14:23:59 +1000, Peter Hutterer wrote: > On Mon, Feb 08, 2016 at 10:00:21PM -0200, Laércio de Sousa wrote: > > Em 8 de fev de 2016 17:54, "Adam Jackson" escreveu: > > > How are you in a scenario where you can pass these values to Xephyr on > > > the command

Re: [PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

On Tue, Feb 09, 2016 at 10:23:05AM -0200, Laércio de Sousa wrote: > Em 9 de fev de 2016 02:24, "Peter Hutterer" > escreveu: > > when we introduced the udev config backend we mostly agreed that we > weren't > > going to use udev as a config storage (which is how

Re: [PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

On Tue, Feb 09, 2016 at 04:59:54PM +0100, Julien Cristau wrote: > On Tue, Feb 9, 2016 at 14:23:59 +1000, Peter Hutterer wrote: > > > On Mon, Feb 08, 2016 at 10:00:21PM -0200, Laércio de Sousa wrote: > > > Em 8 de fev de 2016 17:54, "Adam Jackson" escreveu: > > > > How are you in

Re: [PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

On Mon, Feb 08, 2016 at 10:00:21PM -0200, Laércio de Sousa wrote: > Em 8 de fev de 2016 17:54, "Adam Jackson" escreveu: > > How are you in a scenario where you can pass these values to Xephyr on > > the command line, but can't modify the udev properties? > Well... What I really

Re: [PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

On Fri, Dec 11, 2015 at 11:43:10AM -0200, Laércio de Sousa wrote: > This patch introduces convenient command-line options -xkbrules, > -xkbmodel, -xkblayout, -xkbvariant, and -xkboptions, to set default > values for these properties. > > These options can be handful in cases where corresponding

Re: [PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

On Tue, Feb 09, 2016 at 05:40:26AM -0200, Laércio de Sousa wrote: > Em 9 de fev de 2016 02:24, "Peter Hutterer" > escreveu: > > > > On Fri, Dec 11, 2015 at 11:43:10AM -0200, Laércio de Sousa wrote: > > > This patch introduces convenient command-line options -xkbrules, >

Re: [PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

On Fri, 2015-12-11 at 11:43 -0200, Laércio de Sousa wrote: > This patch introduces convenient command-line options -xkbrules, > -xkbmodel, -xkblayout, -xkbvariant, and -xkboptions, to set default > values for these properties. > > These options can be handful in cases where corresponding values

Re: [PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

Em 8 de fev de 2016 17:54, "Adam Jackson" escreveu: > How are you in a scenario where you can pass these values to Xephyr on > the command line, but can't modify the udev properties? Well... What I really mean is a scenario where neither the Linux distro, nor the keyboard vendor,

[PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

This patch introduces convenient command-line options -xkbrules, -xkbmodel, -xkblayout, -xkbvariant, and -xkboptions, to set default values for these properties. These options can be handful in cases where corresponding values can't be taken from devices' udev properties, and compile-time default