all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 40152@debbugs.gnu.org
Subject: bug#40152: 27.0.90; icomplete vs recursive prompts
Date: Sat, 21 Mar 2020 09:27:44 +0200	[thread overview]
Message-ID: <83k13edv67.fsf@gnu.org> (raw)
In-Reply-To: <87wo7ex4z6.fsf@gmail.com> (message from Kévin Le Gouguec on Fri, 20 Mar 2020 19:21:01 +0100)

> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Date: Fri, 20 Mar 2020 19:21:01 +0100
> 
> - "Synthetic" reproduction recipe:
>     - (completing-read "Foo? " (tags-lazy-completion-table))
> 
> - With actual user commands:
>     - C-x b foo RET
>       - or any non-Lisp buffer, so that xref picks the etags backend
>     - M-.
> 
> >From there:
> 
> - Try to input a character.
>     - The identifier prompt is interrupted by the etags prompt ("Visit
>       tags table").
> - Try to input a character.
>     - The etags prompt disappears and we're back to the identifier
>       prompt.
> 
> The identifier prompt is replaced with the etags prompt as soon as a
> single character is typed.  While in the etags prompt, one can use
> icomplete commands (e.g. TAB, C-.) as well as C-q CHAR to input
> characters one-by-one.

What would you like to happen instead?





  reply	other threads:[~2020-03-21  7:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 18:21 bug#40152: 27.0.90; icomplete vs recursive prompts Kévin Le Gouguec
2020-03-21  7:27 ` Eli Zaretskii [this message]
2020-03-21 12:21   ` Kévin Le Gouguec
2020-03-21 13:36     ` Eli Zaretskii
2020-03-21 20:03       ` Kévin Le Gouguec
2020-09-07  9:11 ` Kévin Le Gouguec
2021-01-24 15:06   ` Kévin Le Gouguec
2021-02-04 18:39     ` Kévin Le Gouguec
2021-08-19 22:05       ` João Távora

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=83k13edv67.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=40152@debbugs.gnu.org \
    --cc=kevin.legouguec@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 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.