From: "Arsen Arsenović" <arsen@aarsen.me>
To: Po Lu <luangruo@yahoo.com>
Cc: Yuan Fu <casouri@gmail.com>,
Theodor Thornhill <theo@thornhill.no>,
emacs-devel@gnu.org
Subject: Re: tree-sitter and Android port
Date: Mon, 20 Feb 2023 16:38:49 +0100 [thread overview]
Message-ID: <86k00cpcbn.fsf@aarsen.me> (raw)
In-Reply-To: <877cwcfmal.fsf_-_@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
Hi,
Po Lu <luangruo@yahoo.com> writes:
> I've added support for tree-sitter to the Android port, and ported that
> library to our Android build system as well.
Thanks, that should greatly improve the efficiency of fontification in
due time.
> However, there is one problem. Android does not let Emacs link with any
> shared libraries or run any executables installed in non-system
> directories, meaning that compiled grammars cannot be installed in a
> useful fashion. This is done for security reasons, as apparently many
> Android programs have been tricked into executing malicious downloaded
> code in the past.
Based on my prior experience with Termux, I suspect that the Emacs home
directory should work. Termux is able to both build and launch programs
in that directory, and I suspect also dlopen () libraries, though I have
not tried that.
> Would one of you two (Yuan Fu or Theodor) please ask the tree-sitter
> developers if there is a way to solve this problem (i.e. by having
> tree-sitter provide a way to ``interpret'' uncompiled grammar files.)
>
> Thanks in advance.
P.S: I noticed that the Termux wiki lists some file managers that
integrate with SAF, and hence, should be able to access the home
directory on devices with poor built-in file managers:
https://wiki.termux.com/wiki/Internal_and_external_storage
While the manual should probably skirt from naming specific file
managers, it could be good to name what a file manager needs to be able
to access the Emacs home directory (namely, SAF support).
Thanks in advance.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2023-02-20 15:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ttzkmrw1.fsf.ref@yahoo.com>
2023-02-17 11:51 ` Android port Po Lu
2023-02-17 12:26 ` Eric S Fraga
2023-02-17 12:56 ` Arsen Arsenović
2023-02-17 13:05 ` Po Lu
2023-02-17 13:21 ` Arsen Arsenović
2023-02-19 11:17 ` Arsen Arsenović
2023-02-19 12:21 ` Po Lu
2023-02-19 14:16 ` Po Lu
2023-02-19 14:40 ` Arsen Arsenović
2023-02-19 15:13 ` Arsen Arsenović
2023-02-20 2:37 ` Po Lu
2023-02-20 15:33 ` Arsen Arsenović
2023-02-20 15:46 ` Po Lu
2023-02-20 16:05 ` Arsen Arsenović
2023-02-19 14:42 ` Arsen Arsenović
2023-02-17 13:50 ` tomas
2023-02-20 14:23 ` tree-sitter and " Po Lu
2023-02-20 15:38 ` Arsen Arsenović [this message]
2023-02-21 2:27 ` Po Lu
2023-02-21 2:56 ` Yuan Fu
2023-02-21 5:33 ` Po Lu
2023-02-21 13:41 ` Po Lu
2023-03-10 20:07 ` Etienne Prud'homme
2023-03-10 23:50 ` Po Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86k00cpcbn.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=theo@thornhill.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).