From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: master 3b41141708: Expose the name of an event's input device to Lisp Date: Fri, 08 Apr 2022 22:52:53 -0400 Message-ID: References: <164933858147.29834.15050766441005536059@vcs2.savannah.gnu.org> <20220407133623.9C209C009A8@vcs2.savannah.gnu.org> <87ee28xyg2.fsf@yahoo.com> <87lewfqf1q.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36393"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 09 04:53:44 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 1nd1EN-0009Ju-FD for ged-emacs-devel@m.gmane-mx.org; Sat, 09 Apr 2022 04:53:43 +0200 Original-Received: from localhost ([::1]:55004 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nd1EM-0005vS-B5 for ged-emacs-devel@m.gmane-mx.org; Fri, 08 Apr 2022 22:53:42 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42344) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nd1Dg-0004Eh-1b for emacs-devel@gnu.org; Fri, 08 Apr 2022 22:53:00 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:20908) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nd1Dd-0002du-8t for emacs-devel@gnu.org; Fri, 08 Apr 2022 22:52:58 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id B98B310020C; Fri, 8 Apr 2022 22:52:55 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 52DF710012E; Fri, 8 Apr 2022 22:52:54 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1649472774; bh=sN9XHhZNFgXC4OJtzCzj6ud/UDgnvKRn233hfim+lec=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=Om353NnwsGWP6fTd9BTnog7X5ltrtRsXfEes4PVF98ikEEWlI2wEFhLxoknKPzB1u fHRDeForvYXVPnMPA90vT7Km1bjjISBUNolHD8N2N9unw3IlMrdIzYIVSIhiDWj0JE kWqH0OYM4ybx7TKWa1Pw3Llnns/Vm7xZvGgwJ57xbAw+bpZOx84QCnN+98u9LZ4KWH 2RQZmf5BelgC6VR6I28605DomlmxHZS2+2DR2attj/AEvR2NGYLUnuteQPjqdDD15j R0q9EulwftfvKOT6+fDII1j982b5ZOXscGE/qcGzuU9qwW3UKzWHYzU9kFbTgx0DMp tJQoAxBfSCBZw== Original-Received: from pastel (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 221DC1201B4; Fri, 8 Apr 2022 22:52:54 -0400 (EDT) In-Reply-To: <87lewfqf1q.fsf@yahoo.com> (Po Lu's message of "Sat, 09 Apr 2022 08:24:49 +0800") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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:287989 Archived-At: >> How 'bout a midway solution: we keep the var but we additionally put >> that info into those events where we can? > > I'm fine with that, but we need a consistent way to get it from the > event structures. Indeed. > WDYT about putting the device in the mouse position list? (Of course, > Eli's concerns about the info itself will have to be addressed.) > > That way, we can have a single function `posn-device' to access the > device. We could put it in the "posn" thingy, but at the same time it's not really a "posn" and it's kinda weird to duplicate it into the start and the end posn of an event. It would be better to associate it with the event itself and have an `event-device` function to access it. Stefan