Gnus development mailing list
 help / color / mirror / Atom feed
From: Bob Newell <bobnewell@bobnewell.net>
To: ding@gnus.org
Subject: Registry save: apparently circular structure being printed
Date: Wed, 18 Jul 2018 20:30:53 -1000	[thread overview]
Message-ID: <CADoYgq90rv=ZRRpTQFdHmNfr-jbiw4miTaZ1bQpFqkPVy0eoRg@mail.gmail.com> (raw)

I came across something that undoubtedly will be hard to reproduce ---
until some ultimately inconvenient moment. I had just set up a half
dozen or so RSS feeds for gnus (using the simple G R method). Now, the
RSS part may or may not be relevant, but I did load a lot of articles
and make a lot of changes to the feeds, killing some, adding some,
etc., for quite a while.

I have code that ensures gnus is properly closed out on exiting Emacs,
and that includes saving the registry (gnus takes care of it on its
own exit, it seems).

At the point of saving the registry, I started getting the message
"Apparently circular structure being printed". This persisted until I
killed emacs directly and deleted the gnus registry. Not exactly an
optimal solution!

I realize this is obscure, and my report is necessarily bare-bones,
but has anyone ever seen anything like this?

In the interim I'm increasing max-lisp-eval-depth from the default 800
to 3000, just before gnus is closed out. I have no idea if this will
be sufficient and will only find out when and if the problem returns.

-- 
Bob Newell
Honolulu, Hawai`i

Via Linux/Emacs/Gnus/BBDB.



             reply	other threads:[~2018-07-19  6:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19  6:30 Bob Newell [this message]
2018-07-19 15:15 ` Eric Abrahamsen
2018-07-31 15:18   ` Tom Tromey
2018-08-01  1:19     ` Eric Abrahamsen
2018-08-01  3:52       ` Tom Tromey

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='CADoYgq90rv=ZRRpTQFdHmNfr-jbiw4miTaZ1bQpFqkPVy0eoRg@mail.gmail.com' \
    --to=bobnewell@bobnewell.net \
    --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).