bug#38457: 27.0.50; dabbrev-expand regression due to message change

[Dmitry Gutov]

On 18.01.2020 11:19, Eli Zaretskii wrote:

> > > > No.  The cursor is always displayed after the overlay string.  If you
> > > > want it to do anything else, you need to put a 'cursor' property on
> > > > the overlay string.
> > >
> > > We do that there.
> >
> > And yet, the message appears before the cursor in the described
> > circumstances.
>
> Can I have a simple reproducer for this, so I could see what's going
> on there?

A couple scenarios:

1. M-x icomplete-mode
2. M-: (run-with-idle-timer 2 nil (lambda () (message "beep")))
2. C-h f
3. Input something that will lead to either [Matched] or [No Matches],
e.g. 'asd'.
4. See [beep] appear before the cursor.

OR

1. M-: (setq resize-mini-windows nil)
2. M-x icomplete-mode
(The same reproduces with Ido with my patch posted)
2. M-: (run-with-idle-timer 2 nil (lambda () (message "beep")))
3. C-h f
4. Input anything at all. E.g. something that will have matches, like 
'ft' or just 'f'.
5. See [beep] appear before the cursor.

Strangely, whether it appears before or after the cursor (at the very 
end of the minibuffer), is affected by the value of 
'resize-mini-windows' (???).