Re: gnus-registry text property removal question (was: [bug]Malformed -*- line)

[CHENG Gao]

*On Wed, 27 Sep 2006 13:20:12 -0400
* Ted Zlatanov <address@hidden> climbed out of the dark hell and cried out:


> I noticed this problem with the gnus-registry before, and I thought
> the set-text-properties call would fix it (it's called before the
> buffer is written).  This is the code:
>
>       (let ((coding-system-for-write gnus-ding-file-coding-system)
>             (standard-output (current-buffer)))
>         (gnus-gnus-to-quick-newsrc-format t "gnus registry startup file" 
> 'gnus-registry-alist)
>         (gnus-registry-cache-whitespace file)
>         (set-text-properties (point-min) (point-max) nil)
>         (save-buffer))
>
> which is run by default when you save (if you customize
> gnus-save-startup-file-via-temp-buffer to be nil, the
> gnus-with-output-to-file working-file routine is called instead, but
> by default it's t).
>
> If this is not the right solution, let me know the proper way to
> eliminate text properties before I write the registry file.  It's OK
> to remove them on ingress into the registry instead; let me know if
> that's better.
>
> I'm asking here because I didn't get a response on the Gnus ding list
> when I asked a while ago; perhaps someone here can answer.

In fact this is just where the problem is.
What I reported is 
(set-text-properties (point-min) (point-max) nil)
does not remove text properties. It should, but it does not.

In my messages I mentioned this port of code. 
I have tracked down to gnus-registry.el (gnus-registry-cache-save,
gnus-registry-trim), and from miswritten entry in .gnus.registry.eld, I
tracked down to emacs/lisp/composite.el where is the only place entry
like
,----
| 0 23 (auto-composed nil)
`----
emerge. Please check function toggle-auto-composition in this file.

That's why I thought toggle auto composition mode off could solve the
problem, but it did not.

Hand said auto-composed is a new Emacs 23 feature. 

I'll build an Emacs 22 to check it again. My experience is Emacs 22 does
not have this problem.