Path: csiph.com!goblin3!goblin.stu.neva.ru!odin.sdfeu.org!.POSTED.norge.sdf.org!not-for-mail From: Fenris Newsgroups: alt.os.linux,comp.os.linux.misc Subject: Re: Xorg Libinput with Static Nodes Followup-To: comp.os.linux.misc Date: Mon, 6 Apr 2020 14:29:09 -0000 (UTC) Organization: SDF Public Access UNIX System, Est. 1987 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Date: Mon, 6 Apr 2020 14:29:09 -0000 (UTC) Injection-Info: odin.sdf-eu.org; posting-host="norge.sdf.org:205.166.94.17"; logging-data="19943"; mail-complaints-to="usenet@odin.sdf-eu.org" User-Agent: slrn/0.9.9p1 (NetBSD) Xref: csiph.com alt.os.linux:64391 comp.os.linux.misc:29671 ["Followup-To:" header set to comp.os.linux.misc.] On 2020-04-06, Rich wrote: > In comp.os.linux.misc F Russell wrote: >> On Mon, 06 Apr 2020 15:53:33 +0200, J.O. Aho wrote: >> >>> >>> they tended to get a new event device id each time you re-plugged them, >>> >> >> That is the general behavior for all USB devices. >> >> But, other than for exceptional circumstances, workstation keyboard >> or mouse are not unplugged and replugged. They are effectively >> permanent attachments. > > But because they *can* be unplugged, the software has to handle the > case when they are unplugged. Because while you might never unplug > them, someone, somewhere, will unplug/replug them. True. My mouse has a bit a broken cable and gets replugged very often. Which is not recognisable since it happens very quickly.