From: CHENG Gao <chenggao@gmail.com>
Subject: Re: gnus-registry: alist-to-hashtable, hashtable-to-alist
Date: Fri, 29 Sep 2006 00:03:00 +0800 [thread overview]
Message-ID: <m2wt7oc72j.fsf@eqiao.com> (raw)
In-Reply-To: <g69ven8t6kg.fsf@CN1374059D0130.kendall.corp.akamai.com>
I trust Gnus hashtb<->alist conversion functions have no problem.
I suspected function gnus-gnus-to-quick-newsrc-format is the culprit.
As Handa said, # (blah blah ...) is representation of string with text
properties.
I had a test by removing all # and leave "0 40 (auto-composed nil)", and
gnus registry works.
In gnus-start.el function gnus-gnus-to-quick-newsrc-format line 2841
,----
| (print-readably t)
`----
I juct checked. At least in my Emacs 23 (06-9-15 cvs), variable
print-readably does not exist.
I nearly damaged my brain by reading code of prin1/princ/print.
At last I think gnus-gnus-to-quick-newsrc-format should be ok. It does
what it should do, even the result is bad.
A silly question:
If an entry in gnus-reristry-alist carries text-property, prin1 will
print it as string and use # as quoting character. Is it right?
If so, I think we need check all puthash (to gnus-registry-hashtb) in
gnus-registry.el for unremoved text property.
My knowledge is not adquate for real useful finding. Wish what I found
can be a little useful to you.
next prev parent reply other threads:[~2006-09-28 16:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 17:15 message registry for Gnus Ted Zlatanov
2003-02-01 10:28 ` Kai Großjohann
2003-02-01 16:39 ` Lars Magne Ingebrigtsen
2003-02-01 20:20 ` Ted Zlatanov
2003-02-02 12:10 ` Lars Magne Ingebrigtsen
2003-02-02 15:14 ` Ted Zlatanov
2003-02-07 12:20 ` Lars Magne Ingebrigtsen
2003-02-02 16:54 ` Kai Großjohann
2003-02-03 20:47 ` Ted Zlatanov
2003-02-04 15:25 ` Simon Josefsson
2003-02-04 19:57 ` Ted Zlatanov
2003-02-05 5:56 ` Simon Josefsson
2003-02-07 20:43 ` Ted Zlatanov
2003-02-02 0:35 ` Raja R Harinath
2003-02-02 1:30 ` Ted Zlatanov
2003-02-02 17:15 ` Raja R Harinath
2003-02-07 20:48 ` Ted Zlatanov
2003-02-07 21:10 ` Lars Magne Ingebrigtsen
2003-02-07 22:45 ` Ted Zlatanov
2003-02-08 20:39 ` Lars Magne Ingebrigtsen
2003-02-21 19:05 ` Ted Zlatanov
2003-02-22 22:20 ` Lars Magne Ingebrigtsen
2003-02-24 15:36 ` Ted Zlatanov
2003-02-24 16:58 ` Andreas Fuchs
2006-09-28 13:20 ` gnus-registry: alist-to-hashtable, hashtable-to-alist (was: message registry for Gnus) Reiner Steib
2006-09-28 14:21 ` gnus-registry: alist-to-hashtable, hashtable-to-alist Ted Zlatanov
2006-09-28 16:03 ` CHENG Gao [this message]
2006-09-28 16:58 ` Reiner Steib
2003-02-24 21:57 ` message registry for Gnus Lars Magne Ingebrigtsen
2003-02-24 22:14 ` Ted Zlatanov
2003-02-25 7:19 ` Kai Großjohann
2003-02-25 17:57 ` Ted Zlatanov
2003-03-28 9:20 ` Ted Zlatanov
2003-04-16 20:35 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2wt7oc72j.fsf@eqiao.com \
--to=chenggao@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).