unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: feature/android b91e8ada70e 3/5: Fix auto-revert-mode on Android
Date: Sat, 25 Feb 2023 12:51:49 +0100	[thread overview]
Message-ID: <877cw6vu7e.fsf@gmx.de> (raw)
In-Reply-To: <87h6va2e1m.fsf@yahoo.com> (Po Lu's message of "Sat, 25 Feb 2023 19:13:41 +0800")

Po Lu <luangruo@yahoo.com> writes:

Hi,

> Hmmm... I'd rather go with modifying C, since the whole point of using
> /content and /assets is to be as transparent as possible towards Lisp.
> IOW, Lisp shouldn't care.  It should get the same results for /assets
> that any other directory gets, except that no file notifications can be
> generated, as /assets cannot change.

My fear is that people could get the same idea of adding hard coded file
names to the C level for similar reasons. And/or that this list changes
for future Android versions, requiring to rebuild Emacs.

A configurable Lisp variable would keep this hassle away from us.

> Thanks.

Best regards, Michael.



  reply	other threads:[~2023-02-25 11:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167724502313.15669.16640007729364817665@vcs2.savannah.gnu.org>
     [not found] ` <20230224132344.40927C1391F@vcs2.savannah.gnu.org>
2023-02-25 10:27   ` feature/android b91e8ada70e 3/5: Fix auto-revert-mode on Android Michael Albinus
2023-02-25 10:41     ` Po Lu
2023-02-25 10:49       ` Michael Albinus
2023-02-25 11:13         ` Po Lu
2023-02-25 11:51           ` Michael Albinus [this message]
2023-02-25 12:19             ` Po Lu
2023-02-25 12:28               ` Michael Albinus
2023-02-26  0:49               ` chad
2023-02-26  2:40                 ` Po Lu
2023-02-27  3:03                   ` chad

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=877cw6vu7e.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    /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).