[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#7053: Reftex is fully broken

From: Alpár Jüttner
Subject: bug#7053: Reftex is fully broken
Date: Sat, 18 Sep 2010 06:19:31 +0200

On Fri, 2010-09-17 at 18:20 +0200, Eli Zaretskii wrote:
> > From: Alpár Jüttner <address@hidden>
> > Cc: address@hidden
> > Date: Fri, 17 Sep 2010 15:49:48 +0200
> > 
> > Here is the GBD trace:
> Thanks.  Unfortunately, this backtrace is not as useful as it could
> be,

I'm sorry. Here comes the lisp backtrace (when pressing C-c = ):

Lisp Backtrace:
"forward-sexp" (0xbfffc9b4)
"backward-sexp" (0xbfffcae4)
---Type <return> to continue, or q <return> to quit---
"latex-backward-sexp-1" (0xbfffcc24)
"byte-code" (0xbfffccd0)
"latex-forward-sexp" (0xbfffcf64)
"forward-sexp" (0xbfffd094)
"byte-code" (0xbfffd140)
"up-list" (0xbfffd3e4)
"byte-code" (0xbfffd490)
"byte-code" (0xbfffd6b0)
"reftex-what-macro" (0xbfffd924)
"reftex-label-location" (0xbfffda64)
"reftex-label-info" (0xbfffdba4)
"byte-code" (0xbfffdc60)
"reftex-parse-from-file" (0xbfffdef4)
"byte-code" (0xbfffdfa0)
"reftex-do-parse" (0xbfffe174)
"reftex-access-scan-info" (0xbfffe2a4)
"reftex-toc" (0xbfffe414)
"call-interactively" (0xbfffe5ac)

And here is another one (typing \ref{valami}, it also freezes reftex):

Lisp Backtrace:
"up-list" (0xbfffcea4)
"byte-code" (0xbfffcf50)
"byte-code" (0xbfffd170)
"reftex-what-macro" (0xbfffd3e4)
"reftex-what-macro-safe" (0xbfffd514)
"reftex-view-crossref" (0xbfffd654)
"byte-code" (0xbfffd700)
"reftex-view-crossref-when-idle" (0xbfffda48)
"apply" (0xbfffda44)
"byte-code" (0xbfffdaf0)
"timer-event-handler" (0xbfffdd94)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]