Re: kill ring menu

[Richard Stallman]

    For instance, here's a random idea (i.e., not well thought out!):
    instead of hardwiring `font-lock-face', how about a buffer-local
    variable that holds `alternative property mappings'?

That seems like a good idea, if it turns out to be clean enough to
implement reliably.

Perhaps it should be done in get-char-property.  That way, you can
still use get-text-property or overlay-get to check the raw data.
This would mean that some programs which now do not use
get-char-property should be changed to use it.  That would probably be
a good idea anyway.

Would it support multiple alternatives for the same property,
or only one?

      It's such a general variable that I would hesitate
    to hardcode font-core.el into pushing ((face font-lock-face)) onto the
    alist, since the user may want their own alternative properties for
    `face', etc...

I don't understand the problem you are worried about.
Could you spell out the scenario, please?