bug#18246: enriched-encode: should set inhibit-point-motion-hooks, too

[Stefan Monnier]

>       the encoded part, it doesn’t yet set inhibit-point-motion-hooks,
>       which easily results in incorrect encoding should text being
>       encoded contain parts protected with the ‘intangible’ property.

`intangible' is evil, nasty, and sucks rocks.
Your patch is probably OK, but even better would be to fix the code that
uses `intangible'.

So, do you happen to know why there was a `intangible' in the way?


        Stefan