all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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:32:18 +0200	[thread overview]
Message-ID: <8737pomlvh.fsf@gmx.net> (raw)
In-Reply-To: <877ff0mlxb.fsf@gmx.net> (Stephen Berman's message of "Wed, 11 May 2016 21:31:12 +0200")

On Wed, 11 May 2016 21:31:12 +0200 Stephen Berman <stephen.berman@gmx.net> wrote:

> On Wed, 11 May 2016 21:11:57 +0200 Michael Albinus <michael.albinus@gmx.de> wrote:
>
>> Stephen Berman <stephen.berman@gmx.net> writes:
>>
>>>> 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.
>>
>> Ahh, that explains what I'm debugging for hours. Your backtrace tells me
>> that Tramp is in completion mode. This couldn't happen when you have
>> entered RET as last key. Entering SPC is another story, which makes more
>> sense with your backtrace.
>
> So sorry that my mistake sent you on a wild good chase.

Oops:                                         goose

>> At least now I have an idea what to look for. And maybe I could even
>> reproduce it locally, which would help much.
>
> That would be good.  I'm now using Gnus from master and having gotten
> the error on first trying to open an article, then using `g' to get the
> correct display as I noted in my previous post, I'm now not getting the
> error anymore at all.  Maybe a timing or initialization issue?
>
>>> 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.
>>
>> I bet you use something like ido or icicles or so.
>
> I don't use either of these directly, but a command I wrote to access
> recentf-list does call ido-completing-read; but I haven't invoked that
> command prior to any of the "Recursive load" errors I've seen in Gnus.
>
> Steve Berman



      reply	other threads:[~2016-05-11 19:32 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
2016-05-11 19:11                                   ` Michael Albinus
2016-05-11 19:31                                     ` Stephen Berman
2016-05-11 19:32                                       ` Stephen Berman [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=8737pomlvh.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.