From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Android port of Emacs Date: Sun, 18 Jun 2023 04:07:52 +0200 Message-ID: <87cz1ta5fr.fsf@telefonica.net> References: <83v8fnslfz.fsf@gnu.org> <83edmask4z.fsf@gnu.org> <5c02371a-3c42-de66-70b7-4ed0d88cc3fa@gutov.dev> <87cz1td0ku.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="8398"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:9h3gYTh83dxofKa0Fn6r/jLz6ZY= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 18 06:45:28 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 1qAkI4-0001yv-Df for ged-emacs-devel@m.gmane-mx.org; Sun, 18 Jun 2023 06:45:28 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qAkH2-0007DQ-R1; Sun, 18 Jun 2023 00:44:24 -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 1qAhpm-00038C-Es for emacs-devel@gnu.org; Sat, 17 Jun 2023 22:08:06 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qAhpk-0007pE-JZ for emacs-devel@gnu.org; Sat, 17 Jun 2023 22:08:06 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qAhpi-0006pq-Jj for emacs-devel@gnu.org; Sun, 18 Jun 2023 04:08:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Sun, 18 Jun 2023 00:44:22 -0400 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:306907 Archived-At: Po Lu writes: > Dmitry Gutov writes: > >> On the flip side, I suppose we should ask how many changes the Android >> port requires in the shared code at all. Because if there were none, >> maintaining the port in a separate repo, rebasing regularly (and >> perhaps automatically), would be a cake walk too. > > The problem with this approach is that such a separate repository will > essentially be a fork. That will be much more difficult for me compared > to keeping it in emacs.git, as it is now: if it does happen, I probably > will have to stop working on one or the other. Why keeping the Android port on its own *branch* prevents it from being on emacs.git? How that prevents distributing source tarballs and binaries targeting Android from the official GNU Emacs site? Keeping the Android port on its own branch even could have advantages from the maintenance POV. The monolithic source model is not always the most effective one. We can try doing an *official* release of Emacs 30 for Android based on the branch and see what happens on terms of user acceptance and developer load, so hopefully after some time the maintainers (and the developer(s)!) have actual facts as a basis for their decisions. Po Lu: I installed your apk on a tablet today. I'm truly impressed, for sure the feat required many ours of research and quite a bit of inventiveness. That said, if my understanding is correct, the port suffers from a serious limitation (imposed by Android, of course) in that the user can't install binaries and use them from Emacs on the usual way. An Emacs that can't invoke git, gcc... is of little use to me, although I'm sure that many users will find the port extremely convenient (Org users, for instance.) Emacs on Termux has no such limitation, but it has its own problems, starting with a terrible user interface. I completely believe you when you say that the port will be maintained. I have more doubts about Android itself, specifically about its increasing restrictions, making Emacs even more constrained with each OS release.