Re: mouse-drag-and-drop-region

[martin rudalics <rudalics@gmx.at>]

 > There's no problem with read-event itself.  The problems is that you
 > can't reliably *un*read an event, so the arguments are against uses of
 > read-event that just "peek" at the next event without the intention to
 > fully consume it.

Couldn't you then write up some text that tells us about the pitfalls of
unreading an event and what should be done instead?  All I found in the
Elisp manual is:

      The reliable and easy way to extract events from a key sequence so
      as to put them in `unread-command-events' is to use
      `listify-key-sequence' (see below).

but I see no explanation how `unread-command-events' can be updated
safely after a `read-event' and whether/when that should be avoided.

Pretty please, martin