Re: keymap in yank-excluded-properties

[Richard Stallman <rms@gnu.org>]

    The decision what to do must be taken when doing the yank (or
    yank-rectangle), rather than the kill or copy, as there just too many
    ways to get the (partial) table into the kill-ring, so the only place
    where it makes sense to determine whether "the thing" is really a
    table is when we yank it.

That seems plausible.

    I still think that my proposal for a yank-function text property (set
    on the original table text, and used by yank and yank-rectangle to do
    the yank) would do be a simple, yet powerful approach, as it would use
    automatically copy that property to the kill-ring, so there is nothing
    we need to add to basic functionality to achieve this.

How about if the two of you together try implementing the yank-function feature
and a suitable function to handle yanking of tables?  That way, we will see
if the feature really can do the job at hand.