GNU bug report logs - #79026
30.1; TAB in Minibuffer when using a quail input-method should complete the longest common suffix of candidates

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Cass Alexandru <g.cassian.alexandru <at> posteo.eu>, Stefan Monnier <monnier <at> iro.umontreal.ca>, Arash Esbati <arash <at> gnu.org>
Cc: 79026 <at> debbugs.gnu.org
Subject: bug#79026: 30.1; TAB in Minibuffer when using a quail input-method should complete the longest common suffix of candidates
Date: Tue, 15 Jul 2025 16:53:23 +0300

> Date: Tue, 15 Jul 2025 08:21:56 +0000
> From: Cass Alexandru <g.cassian.alexandru <at> posteo.eu>
> 
> 1. Steps to reproduce: Type the following in a buffer with `Fundamental` 
> mode:
> ```
> M-x set-input-method RET TeX RET
> \ab
> ```
> 2. Expected behaviour: `TAB` completes to the only possible option 
> (\above) and inserts `┴`.
> 
> 3. Actual behaviour: `TAB` pops up the `*Quail Completions*` buffer with 
> the following content, and I need to fully type out `\above` for `┴` to 
> be inserted in the main buffer:
> ```
> Possible completion and corresponding characters are:
> \ab: -
> \abo: -
> \abov: -
> \above:(1/1) 1.┴
> ```
> 
> My question is: How can I get the expected behaviour instead of the 
> observed one?

It doesn't look like quail-completion (which is the command bound to
TAB in that input method) is supposed to work as you expect.  Instead,
it is a fancy visual feedback for typing long sequences, fancier than
what Emacs usually shows in the echo-area (which is just the list of
candidates for the next character).

IOW, after pressing TAB, you are supposed to:

  . realize that there's just one candidate "\above"
  . type its characters one by one, guided by the moving highlight in
    the *Quail Completions* buffer as you go

Stefan and Arash, am I right?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.