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: Android port of Emacs Date: Sat, 17 Jun 2023 10:27:35 +0300 Message-ID: <83y1kir1js.fsf@gnu.org> References: <83v8fnslfz.fsf@gnu.org> <87fs6reyn0.fsf@yahoo.com> <83a5wysjbf.fsf@gnu.org> <878rcifvaf.fsf@yahoo.com> <831qiashyy.fsf@gnu.org> <87zg4yefb3.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19677"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 17 09:28:15 2023 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 1qAQM2-0004vf-CC for ged-emacs-devel@m.gmane-mx.org; Sat, 17 Jun 2023 09:28:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qAQLS-0006iP-Ey; Sat, 17 Jun 2023 03:27:38 -0400 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 1qAQLR-0006iG-15 for emacs-devel@gnu.org; Sat, 17 Jun 2023 03:27:37 -0400 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 1qAQLQ-0007Bn-O7; Sat, 17 Jun 2023 03:27:36 -0400 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=+4FNqNr9o5kcQJ4dzM3l3gJxJGWBchcvS1e8SwVDAcQ=; b=AJub9DTkLJmX yd72WaQNeUFGoQKisSNy/SQrTMtT9nu57ZsYSis6EtepHGmwyJXMRADaHiFbPZ2ixwxGrC6pGmrBX n5rCMAK3aI+FCOCs6U/mDTQXlW8Y8V8at6W/StOzPAoSCx4LysPoFMEgQbIL+MJ3RmhaLgPXC6jE5 MYzVmxqZJbmlL0+JP/Klby5h6aURPmKuBqbgfkrJ6HMgH/xtUFEA45/mbg2GmIGagqtr6tvO3cyNi LBT7gZWQ27XswUFCpgM2J/DswflG3l4WOhnyjws1hiWuZLvep09xBDMzVlQ/xb7rppBq69bB5iW5r E1T69NUsAK9TAWgZRTQ5ag==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qAQLQ-0001Bb-4k; Sat, 17 Jun 2023 03:27:36 -0400 In-Reply-To: <87zg4yefb3.fsf@yahoo.com> (message from Po Lu on Sat, 17 Jun 2023 15:08:48 +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:306862 Archived-At: > From: Po Lu > Cc: yandros@gmail.com, emacs-devel@gnu.org > Date: Sat, 17 Jun 2023 15:08:48 +0800 > > Eli Zaretskii writes: > > > Those already exist, so we don't need to make any decisions about > > them. That's the difference. > > Were these same concerns not brought to attention when they were > introduced? Not that I know of, no. But that doesn't mean we shouldn't have done that, back then, if the situation was similar. > Or when the PGTK port was first introduced in a significantly worse > state? PGTK is not relevant to this discussion, as I explained in another message. > The Android port is in fact directly pertinent to many of those future > developments in X and GTK: for instance, it is currently not possible to > use Emacs 30 on a X server with only touch-screen input, but it is on > the feature/android branch. That's not relevant: we could merge only those features from the branch. > Some of those changes are quite extensive, and unfortunately, I don't > have the time nor the motivation to separate them from the Android port, > as I don't have the means to test any of them on X. Then I guess they are not so useful on X after all. > > If we don't seriously commit to maintaining it, that follows. > > I will, however. Relying on a single person for developing a significant port is something I would be very uncomfortable about. We have bad experience with that for other ports and significant features. There's no reason to repeat past mistakes if we believe this is a similar situation.