npostavs@users.sourceforge.net writes:

> npostavs@users.sourceforge.net writes:
>
>> I propose adding a new flag print_escape_control_characters instead (see
>> patch #3 in the series).  I also implemented hiding the byte code
>> functions with text properties in #4.  It's not quite satisfactory
>> though, because it doesn't cover byte code functions values that are
>> arguments, only byte code being called.  I think printing needs to be
>> made more flexible in order to cleanly catch all byte code values.
>> Patch #5 replaces NUL bytes with "\0" in X selections (I guess it covers
>> w32 as well? Haven't checked yet).
>
> Updated the patchset to use cl-prin1, now it applies to function values
> in arguments as well.  This one actually doesn't include the byte code
> text at all (path of least resistance: cl-print-object wasn't already
> omitting bytecode and I haven't bothered adding it).

I made use of cl-prin1 depend on a custom option, and replace NUL bytes
also in w32.  I think this is ready to merge now, I will probably do so
sometime next week.