Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Corrupted score files with ... symbols
Date: Tue, 24 Aug 2004 15:55:05 +0900	[thread overview]
Message-ID: <b9yacwlhvp2.fsf@jpl.org> (raw)
In-Reply-To: <b9ysmaevxqq.fsf@jpl.org>

>>>>> In <b9ysmaevxqq.fsf@jpl.org> Katsumi Yamaoka wrote:

>>>>>> In <877jrqf6xn.fsf@deneb.enyo.de>
>>>>>>	Florian Weimer <fw@deneb.enyo.de> wrote:

>> * Katsumi Yamaoka:

>>> The change seems to affect pp (or pp-to-string).  Since pp is
>>> being used also in the other Gnus modules, shouldn't we apply
>>> the same change to them, either?

>> I'm not sure.  `gnus-prin1', for example, has been deliberately
>> written to cope with non-nil values of `print-length'.  Some callers
>> might bind `print-circle' in ddition to `print-length' and try to
>> print cyclic data structures.

> I'm not sure too, but in fact, I saw print-* variables were
> sometimes changed from the default values by a mysterious reason
> even though I never changed them.  I think binding all print-*
> variables to the defaults is better for a prevention for an
> accident and the overhead does not impose a burden because pp is
> not fast.  Isn't it a good opportunity to clear an anxiety away?
> How about making of gnus-pp and gnus-pp-to-string? ;-)

I've done.  I didn't bind `print-circle' because non-nil value
of it is harmless, and it may be useful since it reduces the
size of the .newsrc.eld file, for example.



      reply	other threads:[~2004-08-24  6:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23  9:16 Florian Weimer
2004-08-23  9:46 ` Katsumi Yamaoka
2004-08-23 11:08   ` Florian Weimer
2004-08-23 12:34     ` Katsumi Yamaoka
2004-08-24  6:55       ` Katsumi Yamaoka [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=b9yacwlhvp2.fsf@jpl.org \
    --to=yamaoka@jpl.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).