From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: gnus-registry text property removal question
Date: Thu, 28 Sep 2006 10:35:13 -0400 [thread overview]
Message-ID: <g69r6xwt5y6.fsf@CN1374059D0130.kendall.corp.akamai.com> (raw)
In-Reply-To: <E1GSplm-0007OB-00@etlken>
On 28 Sep 2006, handa@m17n.org wrote:
> In article <E1GSpdJ-0007Hs-00@etlken>, Kenichi Handa <handa@m17n.org> writes:
>
>> In article <ur6xwbl6i.fsf@news.eqiao.com>, CHENG Gao <chenggao@gmail.com>
>> writes:
>>> So if we change
>>> (set-text-properties (point-min) (point-max) nil)
>
>>> to
>>> (buffer-substring-no-properties (point-min) (point-max))
>
>>> it should work right?
>
>> No.
>
> It seems that you don't understand what I wrote repeatedly.
> Ok, I'll change my question.
>
> Gnus somehow gets the string
> "<buohd52j6iy.fsf@dhapc248.dev.necel.com>", and use it as an
> registry entry. Please find where that string is built. I
> guess Gnus uses buffer-substring to get it form some buffer.
> If you find that place, try to replace the function
> buffer-substring with buffer-substring-no-properties.
Gao is trying to help, but misunderstood your message. I think I
understand: by the time the string is printed in the buffer, the text
properties have already been rendered as text. I'll remove string
properties when I get strings into the registry, and for search
strings.
The gnus-registry actually gets the strings from the Gnus internal
data for an article, so it's not a single point where I can change the
code unfortunately. I'll have to go through the library to make sure
properties are removed everywhere.
I'll put the fix into gnus-registry.el in the Gnus tree, and it will
make its way into the Emacs tree from there (I'll make sure it's
backported to Gnus 5.10).
Thanks for all your help, Handa-san :)
Ted
next prev parent reply other threads:[~2006-09-28 14:35 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 ` gnus-registry.el on emacs-unicode-2 (Emacs 23) Reiner Steib
2006-09-28 18:43 ` 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 ` Ted Zlatanov [this message]
2006-09-28 18:41 ` gnus-registry text property removal question 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=g69r6xwt5y6.fsf@CN1374059D0130.kendall.corp.akamai.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).