Eli Zaretskii wrote:
>> From: Sebastien Vauban
>> Cc: 17...@debbugs.gnu.org
>> Date: Thu, 20 Mar 2014 11:30:28 +0100
>>
>> > What we need is names of some Lisp functions, preferably from Org,
>> > that we could then examine in order to look for potential infloops.
>> > That's impossible without L
> From: Sebastien Vauban
> Cc: 17...@debbugs.gnu.org
> Date: Thu, 20 Mar 2014 11:30:28 +0100
>
> > What we need is names of some Lisp functions, preferably from Org,
> > that we could then examine in order to look for potential infloops.
> > That's impossible without Lisp backtrace. To get that,
Juanma Barranquero wrote:
> On Wed, Mar 19, 2014 at 3:57 PM, Sebastien Vauban
> wrote:
>
>> I've had 5 infloops of Emacs, not less.
>
> Where you in the minibuffer? Lately I've had a couple of weird
> infloops apparently related to completion.
Honestly, I don't remember. But, for sure, I wasn't i
On Wed, Mar 19, 2014 at 3:57 PM, Sebastien Vauban
wrote:
> I've had 5 infloops of Emacs, not less.
Where you in the minibuffer? Lately I've had a couple of weird
infloops apparently related to completion.
Eli Zaretskii wrote:
>> From: Sebastien Vauban
>> Date: Wed, 19 Mar 2014 15:57:36 +0100
>>
>> Anyway, here's the backtrace I got:
>
> Thanks for the effort, but as I said several times, such backtraces
> are not useful without the Lisp backtrace part. All I can say from
> this backtrace is that
> From: Sebastien Vauban
> Date: Wed, 19 Mar 2014 15:57:36 +0100
>
> Anyway, here's the backtrace I got:
Thanks for the effort, but as I said several times, such backtraces
are not useful without the Lisp backtrace part. All I can say from
this backtrace is that you were deep inside some hook s