From: Dmitry Gutov <dgutov@yandex.ru>
To: "T.V Raman" <raman@google.com>, emacs-devel@gnu.org
Subject: Re: master@head: completing-read behavior change?
Date: Thu, 23 Jan 2020 00:56:50 +0300 [thread overview]
Message-ID: <f9c0fa91-c4b5-a6ee-d2bf-9be4f52e8dfa@yandex.ru> (raw)
In-Reply-To: <p911rrrf9sc.fsf@retriever.mtv.corp.google.com>
Hi T.V.,
On 23.01.2020 0:42, T.V Raman wrote:
> Could anyone tell me what changed in the behavior of completing-read
> between
> * (HEAD detached at 561ba2633e)
> and HEAD on master branch?
I can't find the revision 561ba2633e, but it could be commit
3b0938c0420de2b845e7e8f8fbbb57ddc61718f2.
> From what I observe, something low-level appears to have changed how
> completing-read produces its final minibuffer prompt when ido is active.
The aforementioned commit changed the way Ido's suggestions are
displayed: instead of being plainly 'insert'-ed, they are now an
'after-string' property on an overlay placed at the end of the prompt
and input.
> From emacspeak, I used to be able to speak the ido choices
> intelligently, now I just get the number of available choices spoken
> -- and the code on the emacspeak end hasn't changed.
Does emacspeak work okay with icomplete-mode? The above is how the
latter has been displaying its suggestions for some time.
This change has been made for better compatibility with the new way
messages are displayed while minibuffer is active (they are displayed
using the same mechanism). So I think emacspeak should learn to
understand this kind of rendering either way.
Sorry for the inconvenience, though.
next prev parent reply other threads:[~2020-01-22 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 21:42 master@head: completing-read behavior change? T.V Raman
2020-01-22 21:56 ` Dmitry Gutov [this message]
2020-01-22 23:53 ` T.V Raman
2020-01-23 0:01 ` T.V Raman
2020-01-23 0:03 ` T.V Raman
2020-01-23 13:58 ` Dmitry Gutov
2020-01-23 14:44 ` T.V Raman
2020-01-23 14:49 ` Dmitry Gutov
2020-01-23 16:45 ` T.V Raman
2020-01-23 17:19 ` Dmitry Gutov
2020-01-22 23:55 ` T.V Raman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9c0fa91-c4b5-a6ee-d2bf-9be4f52e8dfa@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=raman@google.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.