Re: bug#7234: 24.0.50; strange message after text-scale-adjust

[Kenichi Handa <handa@m17n.org>]

In article <jwvpqv4g8r6.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

> > Then, what's the pros and cons of using an overlay map and
> > your set-temporary-overlay-map?

> I think isearch would like to use set-temporary-overlay-map.
> To a large extent they are very similar, but using
> overriding-terminal-local-map means that the non-isearch bindings
> (which cause isearch to exit) are not directly available, so isearch as
> to catch them with a default binding (define-key map [t] ...), then
> exit and push the events on unread-command-events for re-execution.

> And unread-command-events is evil because it's hellishly difficult to
> make it behave 100% correctly in all cases where function-key-map,
> input-decode-map, key-translation-map, keyboard-translate-table,
> input-methods, etc... are involved.

I see.  Thank you for the explanation.

>>> > With that, how to show the prompt?
>>> You'd do it with `message'.
> > Doesn't the message disappear when a command in the
> > temporary overlay-map is executed?

> Yes.  So you only get it at the beginning of the lifetime of the
> temporary-overlay-map, or you have to do extra work to also display it
> later on (e.g. with a post-command-hook:

Ummm, a little bit ugly.

> maybe set-temporary-overlay-map should provide such a
> feature itself, so it's encapsulated).

Yes, that is better.

> As I said, set-temporary-overlay-map barely exists now and while it
> solves some problems, it comes with a new set of problems.  I know its
> good sides (the ones that pushed me to try and play with it) but I'm
> only slowly learning the downsides.

I understand it.

---
Kenichi Handa
handa@m17n.org