RE: `completing-read` without RET

[Drew Adams <drew.adams@oracle.com>]

> > If you hit TAB and there is only one matching candidate, the
> > OP wants that candidate to be chosen (returned).
> 
> Right, that's why I'm saying "use RET not TAB".  AFAIK (s)he never needs
> to use TAB in such completions, always using RET will give h(er|im) the
> behavior (s)he wants (either complete, or select the sole completion).

Naturally you left off the part that was significant here:

  There is a difference between (a) knowing that what you type
  is sufficient to choose a single candidate, and so you hit RET,
  and (b) not knowing whether there is only one match, and maybe
  not even knowing whether completion is lax or REQUIRE-MATCH is
  t, so you hit TAB.

(completing-read "Choose: " '("a" "aa" "b") nil t)

You type `a'.  You don't know what the candidates are, but you
guess that at least one begins with `a'.  If you hit RET then
you get the first candidate, `a'.  If you hit TAB then you see
that there are two matching candidates, `a' and `aa', and you
can choose whichever one you want.

There is NOT a sole candidate that matches your input `a' in
this case.  And what you said is not true in this case:
"either complete, or select the sole completion."  If you use
`a RET' then you get `a' - you see no completions, and what
you get is not the only match.

RET with REQUIRE-MATCHES = t does not respond to what was
requested, IIUC.

I interpret the OP request "doesn't need RET when only one
completion exists" as meaning that the OP (1) does not want
to have to use two keys when only one candidate matches, but
(2) s?he also wants completion - wants to see the matches
when there is more than one.

For vanilla Emacs, neither TAB nor RET does this - in the
general case you need to hit two keys: TAB to complete and
RET to choose.

As I said, if you KNOW that what you type matches only one
candidate then you can just hit RET - of course.  But that
is true regardless of the value of REQUIRE-MATCH.