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: Sun, 25 Jun 2023 08:38:13 +0300 Message-ID: <83y1k8xfsq.fsf@gnu.org> References: <83v8fnslfz.fsf@gnu.org> <83edmask4z.fsf@gnu.org> <5c02371a-3c42-de66-70b7-4ed0d88cc3fa@gutov.dev> <834jn159vs.fsf@gnu.org> <831qi23bif.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="402"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 25 07:39:12 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 1qDISu-000APW-G9 for ged-emacs-devel@m.gmane-mx.org; Sun, 25 Jun 2023 07:39:12 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qDIRy-0002pN-FJ; Sun, 25 Jun 2023 01:38:14 -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 1qDIRs-0002oz-5e for emacs-devel@gnu.org; Sun, 25 Jun 2023 01:38:09 -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 1qDIRr-0001P9-Sb for emacs-devel@gnu.org; Sun, 25 Jun 2023 01:38:07 -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=ZoV02MXPozSiOre3dxF4v7kjmPXA0JjYkTjgNS3Qb7k=; b=fLAEyc2labKi TVAF7B20y2d3bZWZvW24qy9gcye5dABdH9123X4wo1rQxKenEORuQQ+DshW4+4L3H+gAj9vkcDZK4 2WKHHBrMPtxGwend2NUuSe27YpRqdvro0VY0KBGVF0KLbgkNVbamtuxaMsUKqlOMzW91A2g+j0NG+ D7DE1REQ8eSEJAEriH6cnijn0ZPZrSAlP4EQlnE1bKSMuBl/uInrv4wguxNN6gcT0qXYB2vexKjk8 dpvhJerV8sXoTtn4eeOcJduyYEYdziHeZnzrxVD8qvOfGfqFeVbEmFZ0TVKJBgOk6a1I545hwAsHQ 5PUeOsFmc3JGIMY0uu3SUg==; 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 1qDIRg-0003vk-Ru; Sun, 25 Jun 2023 01:37:59 -0400 In-Reply-To: (message from Richard Stallman on Sat, 24 Jun 2023 22:25:48 -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:307207 Archived-At: > From: Richard Stallman > Cc: emacs-devel@gnu.org > Date: Sat, 24 Jun 2023 22:25:48 -0400 > > > (Someone > > brought up redisplay and bidi as such examples, but that's false: > > those are well documented in Emacs and the requisite external > > knowledge is in standard documents that can be studied and understood > > with reasonably small effort. For example, if bidi.c loses its sole > > maintainer, someone could study the UBA in UAX#9 and reimplement it > > from scratch, using the large commentaries in bidi.c and xdisp.c as > > guidance.) > > Could development of the Android port include writing documentation > of the same thoroughness and quality for that code? The main domain-specific knowledge for that port is how Android systems are organized and work, and how application installation works on those systems. Such documentation cannot be usefully part of Emacs, and the parts of it that can and should be in Emacs will have to play the constant catchup game with the changes and developments in the Android OS and environment, something that from my personal experience with an Android-based smartphone changes a lot and at a very fast pace. And it doesn't help that the most crucial information we need for making Emacs a reasonably well-behaved app on Android is on the border of undocumented (if not over the border), as Android AFAIU is not meant to be the host of such programs. So I very much doubt that this particular aspect can be resolved anywhere near completeness by having its documentation in Emacs, let alone keeping that up-to-date to facilitate future development and maintenance.