From c67b74b45ec2e0e450dd25d39554018b539bfd33 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Wed, 8 Nov 2017 21:38:13 +1000 Subject: [PATCH] doc: add a FAQ regarding "please add a configuration option" Signed-off-by: Peter Hutterer --- doc/faqs.dox | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/faqs.dox b/doc/faqs.dox index 3ef4c593..1d5ff3b1 100644 --- a/doc/faqs.dox +++ b/doc/faqs.dox @@ -125,6 +125,20 @@ Changes performed by xinput do not persist across device hotplugs. xinput is considered a debugging and testing tool only and should not be used for permanent configurations. +@section faq_configuration Can you add a configuration option for $FEATURE? + +No. At least that's going to be the initial answer. Read Why +libinput doesn't have a lot of configuration options first. +Configuration options for most features are a signal that we are incapable +of handling it correctly. To get to that point, we want to be sure we're +truly incapable of doing so. libinput has several features that +are handled automatically (and correctly) that users wanted to have +configuration options for initially. + +So the answer to this question will almost always be 'no'. A configuration +option is, in most cases, a cop-out. + @section faq_synclient Why don't synclient and syndaemon work with libinput? Synclient and syndaemon rely on X input device properties that are specific