On 27 Sep 2006, [EMAIL PROTECTED] wrote: > In article <[EMAIL PROTECTED]>, CHENG Gao <[EMAIL PROTECTED]> > writes: > >> While processing registry temp buffer, the code has >> ,---- >> | (set-text-properties (point-min) (point-max) nil) >> `---- >> I changed it to >> ,---- >> | (toggle-auto-composition 0) >> `---- > >> I then tried for some time and got registry file rolled for about ten >> times (I set max registry entries to 25 thus it can roll fast). Seems it >> works well. > > It's just a workaround. The correct fix is to remove text > properties from a string before it is printed in a buffer > that is going to be saved as .gnus.registry.eld, or to fix > reading (or parsing) routine of that file.
Hello, 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. Thanks Ted _______________________________________________ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug