From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: "..." in .marks files
Date: Thu, 15 Nov 2001 19:27:17 +0100 [thread overview]
Message-ID: <ilulmh799fe.fsf@dhcp128.extundo.com> (raw)
In-Reply-To: <s9asnbgn723.fsf@redbull.redback.com> (Istvan Marko's message of "Wed, 14 Nov 2001 17:42:28 -0800")
Istvan Marko <mi-gnus@imarko.dhs.org> writes:
> Every once in a while i end up with an unreadable (to gnus) .marks
> file with "..." in it:
>
> ((read (1 . 2247)) (expire 2121 2170 2173 (2175 . 2180) (2183 . 2184) 2190 (2193 . 2196) (2200 . 2201) (2204 . 2208) ...) (reply 2239) (dormant 2118 2137))
>
> My first thought was that one of the packages I am using must be
> leaking a print-level or print-length setting which affects the princ
> in nnml-save-marks but i can't see any other evidence of this.
>
> I am wondering if anyone else has seen this problem?
>
> Shouldn't gnus-prin1 be used at places like this?
Yes, I changed it to use gnus-prin1.
prev parent reply other threads:[~2001-11-15 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 1:42 Istvan Marko
2001-11-15 18:27 ` Simon Josefsson [this message]
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=ilulmh799fe.fsf@dhcp128.extundo.com \
--to=jas@extundo.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).