From: "Alpár Jüttner" <alpar@cs.elte.hu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: auctex-devel@gnu.org, 7053@debbugs.gnu.org,
Carsten Dominik <dominik@science.uva.nl>
Subject: bug#7053: Reftex is fully broken
Date: Sun, 19 Sep 2010 07:24:13 +0200 [thread overview]
Message-ID: <1284873853.3330.55.camel@piko.site> (raw)
In-Reply-To: <83mxrfz9se.fsf@gnu.org>
> Thanks. It sounds like the problem is in reftex-what-macro. I'm
> CC'ing the reftex author and maintainers in the hope that they can
> find the culprit.
>
> Failing that, perhaps you could do a "bzr bisect" to find the revision
> which broke reftex.
I try to avoid to do it as far as I can. I'm a big fan of distributed
version control systems. I use hg in several project with grate success
and satisfaction. I people have also very good experience with git.
But bzr is so much pain to use. A 'bzr pull' triggers tens of MB net
traffic every time (and takes long minutes), operations that are
instantaneous on hg/git takes ages here (log, update, status, diff).
I simply can't understand why emacs chose bzr.
Regards,
Alpar
>
> Thanks.
>
> >
> > 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)
> > (gdb)
> >
> > 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)
> > (gdb)
> >
> > Regards,
> > Alpar
> >
> >
>
next prev parent reply other threads:[~2010-09-19 5:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 9:41 bug#7053: Reftex is fully broken Alpár Jüttner
2010-09-17 11:52 ` Eli Zaretskii
2010-09-17 13:49 ` Alpár Jüttner
2010-09-17 16:20 ` Eli Zaretskii
2010-09-18 4:19 ` Alpár Jüttner
2010-09-18 9:21 ` Eli Zaretskii
2010-09-18 14:47 ` Stefan Monnier
2010-09-19 5:34 ` Alpár Jüttner
[not found] ` <83mxrfz9se.fsf@gnu.org>
2010-09-18 15:16 ` bug#7053: [AUCTeX-devel] " Ralf Angeli
[not found] ` <87vd635bfi.fsf@caeruleus.net>
2010-09-18 16:11 ` Stefan Monnier
[not found] ` <jwv62y39gts.fsf-monnier+emacs@gnu.org>
2010-09-18 16:28 ` Ralf Angeli
2010-09-19 8:48 ` Andreas Röhler
2010-09-20 23:40 ` Stefan Monnier
2010-09-19 5:24 ` Alpár Jüttner [this message]
2010-09-19 5:58 ` Eli Zaretskii
[not found] ` <E1OxCvN-0001nb-Jl@fencepost.gnu.org>
2010-09-19 6:42 ` Alpár Jüttner
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=1284873853.3330.55.camel@piko.site \
--to=alpar@cs.elte.hu \
--cc=7053@debbugs.gnu.org \
--cc=auctex-devel@gnu.org \
--cc=dominik@science.uva.nl \
--cc=eliz@gnu.org \
/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.