From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Brian Cully Newsgroups: gmane.emacs.devel Subject: Re: master 3b41141708: Expose the name of an event's input device to Lisp Date: Sat, 09 Apr 2022 22:45:02 -0400 Message-ID: <87zgktabcp.fsf@ditto.jhoto.spork.org> References: <164933858147.29834.15050766441005536059@vcs2.savannah.gnu.org> <83a6cway59.fsf@gnu.org> <87tub4uivu.fsf@yahoo.com> <83y20fakwn.fsf@gnu.org> <87o81bu7zj.fsf@yahoo.com> <83v8vjai4s.fsf@gnu.org> <87bkxbsqfl.fsf@yahoo.com> <835yniah0u.fsf@gnu.org> <8735impqw4.fsf@yahoo.com> <83v8vi8uyu.fsf@gnu.org> <871qy6o9p3.fsf@yahoo.com> <83o81a8qnd.fsf@gnu.org> <87zgkulbuu.fsf@yahoo.com> <83ilri8iag.fsf@gnu.org> <87k0by43an.fsf@gnus.org> <838rse89vr.fsf@gnu.org> <87czhqb0l2.fsf@ditto.jhoto.spork.org> <87k0bxkbbq.fsf@yahoo.com> <874k31bsvw.fsf@ditto.jhoto.spork.org> <871qy5it5x.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36379"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.6.10; emacs 29.0.50 Cc: Eli Zaretskii , monnier@iro.umontreal.ca, Lars Ingebrigtsen , rms@gnu.org, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Apr 10 05:05:45 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ndNtZ-0009CD-BD for ged-emacs-devel@m.gmane-mx.org; Sun, 10 Apr 2022 05:05:45 +0200 Original-Received: from localhost ([::1]:42268 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ndNtY-0001Hk-1n for ged-emacs-devel@m.gmane-mx.org; Sat, 09 Apr 2022 23:05:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52446) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ndNs1-0000Zd-21 for emacs-devel@gnu.org; Sat, 09 Apr 2022 23:04:09 -0400 Original-Received: from coleridge.kublai.com ([166.84.7.167]:59977 helo=mail.spork.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ndNry-0005Tf-U8; Sat, 09 Apr 2022 23:04:08 -0400 Original-Received: from ditto (unknown [IPv6:2001:470:1f07:1b9:8650:a942:ec5e:856b]) by mail.spork.org (Postfix) with ESMTPSA id 22ABF3423; Sat, 9 Apr 2022 23:03:34 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=spork.org; s=dkim; t=1649559845; bh=stA8pmqXI6KPbJceCtOAm/IMIihy6uOQUonASp8rUeQ=; h=References:From:To:Cc:Subject:Date:In-reply-to; b=oflVP3UVh8dtxzYQeBKKOJNl8Kz8z29TAT7MY29mVaX/ya1hkzGWrpdMjSN+9hnFG ErlQ73551u0Ar6dRtU/Cf+re8Hvoj+tpA0gRxDCPyoHk7cPfIiILKFAAJqG0EFhOX9 jVRRU/+zdwWyTB9YHCKdqpXtPigpAV8Ty7HCstwQ= In-reply-to: <871qy5it5x.fsf@yahoo.com> Received-SPF: pass client-ip=166.84.7.167; envelope-from=bjc@spork.org; helo=mail.spork.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:288087 Archived-At: Po Lu writes: > No, Lisp code will decide based on the class of your device (on X, > that's calculated based on the name) _and_ the events it is currently > generating that it has capabilities x, y and z. This is what=E2=80=99s not clear to me. Is Lisp code that=E2=80=99s shippi= ng as part of the standard Emacs distribution making this classification, or am I doing it in my user customizations? My understanding is that X (and Wayland) pull their classification from evdev/libinput, which itself pulls from the HID descriptors. The name of the device doesn=E2=80=99t figure, except for thin= gs like desktop input settings panels, as a way to differentiate devices. I can (and do!) change how some of my USB devices present themselves without changing their names. I=E2=80=99ve never had any kind of issue, so I=E2=80=99m not sure why the name would be considered important information in terms of classification. I /do/ see the value for user customization, similar to how desktop input settings also differentiate devices based on their name to customize behavior, but this seems to me to be a user-level concern, as long as there is machinery to support it. If that=E2=80=99s what you=E2=80= =99ve been suggesting, I apologize, as I haven=E2=80=99t read it as such (perhaps I=E2= =80=99ve missed the forest for the trees here). -bjc