Yet another problem with default-text-properties

Yet another problem with default-text-properties

[Luc Teirlinck]

Consider the following ielm run:

*** Welcome to IELM ***  Type (describe-mode) for help.
ELISP> (make-local-variable 'default-text-properties)
default-text-properties
ELISP> (setq default-text-properties '(foo 69))
(foo 69)

ELISP> (setq char-property-alias-alist '((foo bar)))
((foo bar))

ELISP> (setq str "01")
"01"
ELISP> (get-text-property 1 'foo str)
69
ELISP> 

Now this might look perfectly as expected.

However, does this mean that whenever one constructs any strings, or
calls any command that could be constructing strings, that are not
directly related to the current buffer's mode, one should always bind
default-text-properties to nil?  For instance, enriched mode specifies
a buffer-local value for default-text-properties.  That value seems to
be meant for text to be inserted in the buffer, but it will also apply
to completely unrelated strings constructed while the buffer is
current.

Does that not seem somewhat bizarre?

Sincerely,

Luc.

Re: Yet another problem with default-text-properties

[Richard Stallman]

    However, does this mean that whenever one constructs any strings, or
    calls any command that could be constructing strings, that are not
    directly related to the current buffer's mode, one should always bind
    default-text-properties to nil?

I don't think so.  The text properties of text in a string should
mean the same as in a buffer.

However, this means that default-text-properties probably should not
have local bindings.