From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: "Final" version of tty child frames Date: Wed, 18 Dec 2024 15:54:39 +0200 Message-ID: <86ikrhm6zk.fsf@gnu.org> References: <86wmi0g0x6.fsf@gnu.org> <11a86987cce9fe0a257c3fa58703dc33@finder.org> <86wmgl6jzv.fsf@gnu.org> <092cb755eee3a9b5e06d15c0b07e90b1@finder.org> <276414b03c24964aaeb9e43e8dba5e77@finder.org> <5fedec86bce470555814acbdf999f99d@finder.org> <86h6791khk.fsf@gnu.org> <09b0904da92efad899865b2ece5f3116@finder.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7382"; mail-complaints-to="usenet@ciao.gmane.io" Cc: gerd.moellmann@gmail.com, emacs-devel@gnu.org, rudalics@gmx.at To: Jared Finder , Stefan Kangas , Andrea Corallo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Dec 18 14:56:19 2024 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 1tNuXD-0001jA-2O for ged-emacs-devel@m.gmane-mx.org; Wed, 18 Dec 2024 14:56:19 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tNuWQ-0002lt-0w; Wed, 18 Dec 2024 08:55:30 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tNuWL-0002jv-HV for emacs-devel@gnu.org; Wed, 18 Dec 2024 08:55:26 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tNuWI-0002oL-Q5; Wed, 18 Dec 2024 08:55:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=/ZuNpPAfppu65vU6hm747w+J+TaFf+q/487xhpzT5k8=; b=o2Ty3VTRNc1V D632tqCzMv/KNljYgcPa1s8u2tyOWoVs0Wr5uD+zz2Q+h1Xrn/wGB+LHTXEZHuT6Cy6ymuOVGLhZd 7x3LJj/O65idH3Da0fhs6YnKhKL78b88YREYjpNL227D+q213fQSozJMQtyvNVNgIBsIaQTIyQ887 VlekPxnHv1yFCJOB59B9wjmbYTCnwiQGpEee4h19LhLy//I23pNxLF9kFLfGyWSm4uu+wb19S+3sy Nxf7ekgrlp5fbD+UGvMwOkn/tdKHXlHsBXYTClcO27SZnQEldH71qfunNDzm/aE+adW28JWgQE1nI 7xSs2BrJFqP5jfVPjBPBug==; In-Reply-To: <09b0904da92efad899865b2ece5f3116@finder.org> (message from Jared Finder on Tue, 17 Dec 2024 21:35:35 -0800) 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:326652 Archived-At: > Date: Tue, 17 Dec 2024 21:35:35 -0800 > From: Jared Finder > Cc: Eli Zaretskii , emacs-devel@gnu.org, rudalics@gmx.at > > Things otherwise seem fine with tty child frames. There's certainly > oddness with mouse interaction, but it's not fundamentally broken in any > way, just more things that don't work. In particular: > > With xterm-mouse, as I highlighted earlier, I can select the child frame > even if it is set as not selectable. Once a window in a child frame is > selected, I can type there normally. > > With gpm mouse, I have the opposite problem. I can never select the > child frame and in fact the mouse behaves as if the child frame isn't > there. Clicking and tooltip text both pay no attention to the child > frame and just act on whatever is behind the child frame. > > For both of these, I couldn't get mouse-face or clicking to work on > child frames. I was doing the following: > > (setq button (buttonize "[Click me]" (lambda (&rest _) (message > "Clicked!")))) > (posframe-show " *buffer*" :string (concat "A\n" button "\nB")) > > The posframe would show, but the mouse can't interact with the > buttonized text. This may be a limitation of posframe though, it also > didn't work in graphical mode. > > That's really it. I don't see any major issues with child frames. As > long as we're ok with saying that mouse support is not mature, it seems > fine to me. If we don't see immediate ways of fixing some of these issues, I think it should be okay to land this on master, if Stefan and Andrea agree. Thanks.