From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: emacs-pretest-bug@gnu.org, ding@gnus.org
Subject: Re: gnus-registry.el on emacs-unicode-2 (Emacs 23)
Date: Thu, 28 Sep 2006 19:08:06 +0200 [thread overview]
Message-ID: <v9r6xvudft.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m2hcytjr4o.fsf@eqiao.com> (CHENG Gao's message of "Wed\, 27 Sep 2006 22\:55\:35 +0800")
On Thu, Sep 28 2006, CHENG Gao wrote:
[ ... in an unrelated thread: <news:m2wt7oc72j.fsf@eqiao.com>
<http://thread.gmane.org/m2wt7oc72j.fsf@eqiao.com>.
No trimming any quotes. ]
> I trust Gnus hashtb<->alist conversion functions have no problem.
Yes, my article on this was unrelated to your 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),
Could you please try if the problem also exists in Emacs 22 (trunk)?
As I understand from the previous messages, it only exists in
emacs-unicode-2 (Emacs 23). Is this correct? Then I could remove it
from the list of release-relevant bugs for Emacs 22
(admin/FOR-RELEASE).
> variable print-readably does not exist.
It exist in XEmacs; If it doesn't exist in Emacs, it is simply
ignored. No problem.
I don't know about the rest of your questions:
> 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.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-09-28 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m37izsx28r.fsf@sl392.st-edmunds.cam.ac.uk>
[not found] ` <E1GRdu3-0001cN-00@etlken>
[not found] ` <ufyegboyc.fsf@news.eqiao.com>
[not found] ` <E1GSBLt-0004R0-00@etlken>
[not found] ` <m2u02usrmr.fsf@eqiao.com>
[not found] ` <m2mz8msjey.fsf@eqiao.com>
[not found] ` <m2irjatuek.fsf@eqiao.com>
[not found] ` <E1GSOhd-0006lo-00@etlken>
[not found] ` <uac4mnjez.fsf@news.eqiao.com>
[not found] ` <E1GSPRU-0007Ka-00@etlken>
[not found] ` <ud59ij6nq.fsf@news.eqiao.com>
[not found] ` <E1GSRA4-0000HP-00@etlken>
[not found] ` <uejtx519t.fsf@news.eqiao.com>
[not found] ` <E1GSSdJ-0001Tm-00@etlken>
[not found] ` <u64f9203s.fsf@news.eqiao.com>
[not found] ` <E1GSYk0-0000MT-00@etlken>
[not found] ` <m2ejtx79k4.fsf@eqiao.com>
2006-09-27 14:43 ` gnus-registry.el on emacs-unicode-2 (Emacs 23) (was: [bug]Malformed -*- line) Reiner Steib
2006-09-27 14:55 ` CHENG Gao
2006-09-28 17:08 ` Reiner Steib [this message]
2006-09-28 18:43 ` gnus-registry.el on emacs-unicode-2 (Emacs 23) Ted Zlatanov
2006-09-29 3:09 ` CHENG Gao
2006-09-28 2:14 ` gnus-registry.el on emacs-unicode-2 (Emacs 23) (was: [bug]Malformed Richard Stallman
[not found] ` <g69lko5w7jn.fsf_-_@CN1374059D0130.kendall.corp.akamai.com>
[not found] ` <u3bachfrs.fsf@news.eqiao.com>
[not found] ` <E1GSnBy-0003Ow-00@etlken>
[not found] ` <ur6xwbl6i.fsf@news.eqiao.com>
[not found] ` <E1GSpdJ-0007Hs-00@etlken>
[not found] ` <E1GSplm-0007OB-00@etlken>
2006-09-28 14:35 ` gnus-registry text property removal question Ted Zlatanov
2006-09-28 18:41 ` 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=v9r6xvudft.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.org \
/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).