unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Milan Zamazal <pdm@zamazal.org>, 65370@debbugs.gnu.org
Subject: bug#65370: 30.0.50; Android: Single key input doesn’t work in some situations
Date: Sun, 03 Sep 2023 08:55:22 +0800	[thread overview]
Message-ID: <875y4sm5xh.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmm8ee+E-GwicCZ-hs-gqAZG6hTdkRZbmff3N03ecLddZw@mail.gmail.com> (Stefan Kangas's message of "Sat, 2 Sep 2023 09:31:45 -0700")

Stefan Kangas <stefankangas@gmail.com> writes:

> Po Lu <luangruo@yahoo.com> writes:
>
>> Milan Zamazal <pdm@zamazal.org> writes:
>>
>>> In some cases, minibuffer prompts expecting a single key response don't
>>> work.  I don't know whether it's actually Android specific but I've
>>> observed it there.
>>>
>>> I have two reproducible examples when this happens:
>>>
>>> 1. In Dired, when trying to copy a file (using `C' key) to another file
>>>    that already exists, Dired asks for confirmation with the "yn!q"
>>>    prompt.  It's possible to type multiple characters into the prompt,
>>>    the typed characters appear there, but nothing else happens.  I have
>>>    to use C-g to quit.  Instead, the prompt should react to the first
>>>    typed character.
>>>
>>> 2. When running `M-x org-drill' on an org-drill file (org-drill is
>>>    available from MELPA and
>>>    https://gitlab.com/phillord/org-drill#demonstration describes an easy
>>>    way to try it), one can normally type digits 1-5 to proceed with the
>>>    cards.  Instead, the prompt doesn't react to keys at all and when I
>>>    click to the primary buffer, the typed characters are inserted there.
>>>    Both is wrong and doesn't happen in (non-Android) Emacs 29.1.
>>
>> Thanks, both of these issues should be fixed soon.  They're particular
>> to the Android port, more specifically its input method text conversion
>> features.
>
> Is there anything more to do here, or should this be closed?

Nothing other than waiting for a reply from Milan.





  reply	other threads:[~2023-09-03  0:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 17:36 bug#65370: 30.0.50; Android: Single key input doesn’t work in some situations Milan Zamazal
2023-08-19  0:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 16:31   ` Stefan Kangas
2023-09-03  0:55     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-03  7:13       ` Stefan Kangas
2023-09-03 10:04         ` Milan Zamazal
2023-09-03 10:39           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=875y4sm5xh.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=65370@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=pdm@zamazal.org \
    --cc=stefankangas@gmail.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).