unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: chad <yandros@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: feature/android b91e8ada70e 3/5: Fix auto-revert-mode on Android
Date: Sun, 26 Feb 2023 22:03:15 -0500	[thread overview]
Message-ID: <CAO2hHWbNX9Hm=MPG0YKPTq=MRmNq5Qvb_7+aUfTcyOJ61NXEcQ@mail.gmail.com> (raw)
In-Reply-To: <87r0ud1749.fsf@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 984 bytes --]

On Sat, Feb 25, 2023 at 9:41 PM Po Lu <luangruo@yahoo.com> wrote:

> chad <yandros@gmail.com> writes:
>
> > If these names are strictly by and for emacs, maybe their names should
> > reflect that somehow? (Sorry to start a naming sub-thread...)
>
> Changing their names to not look like directories will miss the whole
> point of having assets and content providers under directories, so no.
>

I think there is a miscommunication; I intended to suggest that the names
could reflect the fact that they were by and for emacs, not that the names
should not look like directories. Nearly all of my computers have _many_
directories with names that look like directories and are clearly by and
for emacs, so this seemed like a reasonable suggestion. Perhaps there's
some reason unknown to me that these directories need to look like they're
part of general system services (similar to /proc and /mnt, as demonstrated
up-thread); in that case, please pardon the suggestion.

Thanks,
~Chad

[-- Attachment #2: Type: text/html, Size: 1470 bytes --]

      reply	other threads:[~2023-02-27  3:03 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
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 [this message]

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='CAO2hHWbNX9Hm=MPG0YKPTq=MRmNq5Qvb_7+aUfTcyOJ61NXEcQ@mail.gmail.com' \
    --to=yandros@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=michael.albinus@gmx.de \
    /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).