From: Lars Ingebrigtsen <larsi@gnus.org>
To: Wes Hardaker <wes@hardakers.net>
Cc: ding@gnus.org
Subject: Re: large number of References: breaks gnus when tramp is in use
Date: Mon, 26 Jan 2015 14:31:17 +1100 [thread overview]
Message-ID: <87y4oqjjzu.fsf@building.gnus.org> (raw)
In-Reply-To: <0loaqvlpkx.fsf@wjh.hardakers.net> (Wes Hardaker's message of "Mon, 22 Dec 2014 06:35:42 -0800")
Wes Hardaker <wes@hardakers.net> writes:
> When entering a (nnmaildir) group with a references header (pretty much
> always spam) that contains a huge number of ids, entering the group
> crashes with:
>
> tramp-completion-file-name-handler: Variable binding depth exceeds
> max-specpdl-size
[...]
> So, the odd thing to me is why is the tramp hook being called for the
> references header in the first place? Is that message id trying to be
> file-opened? And if so, why?
Yeah, this seems like a Tramp bug of some kind. If you set
`debug-on-error', are you able to get a backtrace? That might give us a
clue as to what is calling Tramp here.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2015-01-26 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 14:35 Wes Hardaker
2015-01-26 3:31 ` Lars Ingebrigtsen [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=87y4oqjjzu.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=wes@hardakers.net \
/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).