From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: annoying breaks in the gnus registry file
Date: 18 Apr 2006 17:08:29 -0400 [thread overview]
Message-ID: <4n4q0q7fsi.fsf@asimov.bwh.harvard.edu> (raw)
In-Reply-To: <m3y7y88dr2.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Fri, 14 Apr 2006 15:53:37 +0200")
On 14 Apr 2006, larsi@gnus.org wrote:
> "Ted Zlatanov" <tzz@lifelogs.com> writes:
>
>> Occasionally I'll save this to the Gnus registry file, which breaks it:
>>
>> ("<200505101018.j4AAIDsw021967@relay9.bu.edu>" ((mtime 17024 47890 802976)
>> (process (spam spam-use-move "nnimap+lifelogs.com:INBOX.spam"))
>> (sender . "<preprogrammed@ctlnet.com>") (subject . #
>> ("Нет \xc3\x90\xc2\xb2ысшего обр\xc3\x90\xc2\xb0зовани\xc3\x91 =?utf-8?q?=8F? =D0=9C=D1=8B =D0?= \xc2\xbfоможем Вам" 0 4 nil 4 6 (display "\\320" help-echo utf-8-help-echo untranslated-utf-8 208) 6 8
>
> [...]
>
>> So I want to transform the text
>> before I hand it over to that function.
>
> I think the problem is text properties. Try running the strings
> through `remove-text-properties' before putting them into the list.
I fixed that when saving via the temp buffer. It's harder to do it in
the other case - can I modify the gnus-with-output-to-file function?
Ted
next prev parent reply other threads:[~2006-04-18 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 15:51 Ted Zlatanov
2006-04-14 13:53 ` Lars Magne Ingebrigtsen
2006-04-18 21:08 ` Ted Zlatanov [this message]
2006-04-21 23:50 ` Lars Magne Ingebrigtsen
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=4n4q0q7fsi.fsf@asimov.bwh.harvard.edu \
--to=tzz@lifelogs.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).