From: Lynn Winebarger <owinebar@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Android input methods (was: Re: textconv.c)
Date: Sun, 12 Feb 2023 11:00:20 -0500 [thread overview]
Message-ID: <CAM=F=bAGd=dK8drHsSEfRFKKzab3Nye11T6R+8TP=2RY2onODg@mail.gmail.com> (raw)
In-Reply-To: <87bklyzyyj.fsf_-_@yahoo.com>
On Sun, Feb 12, 2023 at 10:30 AM Po Lu <luangruo@yahoo.com> wrote:
>
> Now, it is sometimes possible to disable the input method and to simply
> work with an on screen keyboard (which is what the Android port
> currently does), but that precludes entering any non-ASCII text, and is
> a luxury which is only affored by several input methods. Also, it
> wouldn't be out of character for GNOME to demand applications implement
> input method support their ``right way'' either, at some point in the
> future, so we will have to implement this properly, if not now, then at
> some point in the future.
Interesting. As a user, it sounds like Emacs ought to make itself
available as one of those input methods, rather than delegating its
editing functions to other "input methods".
Lynn
prev parent reply other threads:[~2023-02-12 16:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 12:58 textconv.c Eli Zaretskii
2023-02-12 14:05 ` textconv.c Po Lu
2023-02-12 14:32 ` textconv.c Eli Zaretskii
2023-02-12 15:06 ` textconv.c Eli Zaretskii
2023-02-12 15:35 ` textconv.c Po Lu
2023-02-12 15:27 ` Android input methods (was: Re: textconv.c) Po Lu
2023-02-12 15:57 ` Eli Zaretskii
2023-02-13 2:21 ` Android input methods Po Lu
2023-02-13 13:49 ` Eli Zaretskii
2023-02-13 14:37 ` Po Lu
2023-02-13 15:17 ` Eli Zaretskii
2023-02-13 17:04 ` Eli Zaretskii
2023-02-14 1:57 ` Po Lu
2023-02-14 14:32 ` Eli Zaretskii
2023-02-14 15:14 ` Po Lu
2023-02-14 17:01 ` Eli Zaretskii
2023-02-15 2:13 ` Po Lu
2023-02-12 16:00 ` Lynn Winebarger [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='CAM=F=bAGd=dK8drHsSEfRFKKzab3Nye11T6R+8TP=2RY2onODg@mail.gmail.com' \
--to=owinebar@gmail.com \
--cc=eliz@gnu.org \
--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).