From: Stephen Berman <stephen.berman@gmx.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Kaushal Modi <kaushal.modi@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Emacs developers <emacs-devel@gnu.org>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: Recursive load? master build fail
Date: Wed, 11 May 2016 21:02:13 +0200 [thread overview]
Message-ID: <87bn4cmn9m.fsf@gmx.net> (raw)
In-Reply-To: <87bn4cy6md.fsf@gmx.de> (Michael Albinus's message of "Wed, 11 May 2016 17:08:42 +0200")
On Wed, 11 May 2016 17:08:42 +0200 Michael Albinus <michael.albinus@gmx.de> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> I updated my master branch to 62d7acae7405732268713006d839a5c3507b9482
>> and built with `make bootstrap', and when I try to open an article in
>> Gnus (by typing RET on the article's line in the Summary buffer), a
>> "Recursive load" error in Tramp is signalled and the article is not
>> displayed; full backtrace attached. If I type `C-u g' to open the
>> article, then it is displayed.
>
> I cannot reproduce it here. Does it also happen, when you call "emacs -Q",
> and load only gnus specific settings?
No, with -Q, `M-x gnus', `n', `B RET news.gmane.org RET', then entering
e.g. the group gmane.emacs.bugs and selecting an article with SPC (not
RET, as I mistakenly wrote above) works without error. So it's only
with my setup that I get the "Recursive load" error; however, I now
discovered that when I quit the backtrace buffer that pops up (I have
debug-on-error set) and then type `g' on the article in the Summary
buffer, then the article is displayed as usual. Trying to open further
articles then sometimes works immediately and sometimes errors,
sometimes as before but also like this (just displayed in the echo
area not in a backtrace buffer):
Error while decoding: (error Recursive load /data/steve/git/emacs-master/lisp/net/tramp.elc /data/steve/git/emacs-master/lisp/net/tramp.elc /data/steve/git/emacs-master/lisp/net/tramp.elc /data/steve/git/emacs-master/lisp/net/tramp.elc /data/steve/git/emacs-master/lisp/net/tramp.elc /data/steve/git/emacs-master/lisp/mail/qp.elc)
> It looks also a bit strange, that file-truename uses some
> hidden arguments, which are not propagated to Tramp:
>
>> tramp-completion-file-name-handler(file-truename "/data")
>> file-truename("/data" (93) (nil))
>> file-truename("/data/steve" (93) (nil))
>> file-truename("/data/steve/git" (93) (nil))
>> file-truename("/data/steve/git/emacs-master" (93) (nil))
>> file-truename("/data/steve/git/emacs-master/lisp" (93) (nil))
>> file-truename("/data/steve/git/emacs-master/lisp/net" (93) (nil))
>> file-truename("/data/steve/git/emacs-master/lisp/net/tramp.elc")
I have no idea what that means. Do you have any suggestion how to try
to debug this? I can try to bisect my initializations, but that will be
laborious; git bisect will probably be even more painful, since building
Emacs on this machine is quite slow.
Steve Berman
next prev parent reply other threads:[~2016-05-11 19:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 21:58 Recursive load? master build fail Kaushal Modi
2016-05-07 23:27 ` Dmitry Gutov
2016-05-08 0:08 ` Paul Eggert
2016-05-08 1:22 ` Kaushal Modi
2016-05-08 1:31 ` Kaushal Modi
2016-05-08 1:56 ` Paul Eggert
2016-05-08 7:17 ` Paul Eggert
2016-05-08 7:55 ` Michael Albinus
2016-05-08 9:50 ` Michael Albinus
2016-05-08 14:24 ` Kaushal Modi
2016-05-08 19:00 ` Colin Baxter
2016-05-11 5:22 ` Colin Baxter
2016-05-08 19:13 ` Paul Eggert
2016-05-08 22:06 ` Michael Albinus
2016-05-09 6:43 ` Paul Eggert
2016-05-09 7:23 ` Michael Albinus
2016-05-11 6:17 ` Paul Eggert
2016-05-11 7:23 ` Michael Albinus
2016-05-11 9:45 ` Stephen Berman
2016-05-11 15:08 ` Michael Albinus
2016-05-11 19:02 ` Stephen Berman [this message]
2016-05-11 19:11 ` Michael Albinus
2016-05-11 19:31 ` Stephen Berman
2016-05-11 19:32 ` Stephen Berman
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=87bn4cmn9m.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=dgutov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=michael.albinus@gmx.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.