From: Rudolfo Ungern <rolf_unger@hotmail.com>
To: help-gnu-emacs@gnu.org
Cc: bug-cc-mode@gnu.org
Subject: Re: imenu with cc-mode in emacs 22 (win32)
Date: Wed, 12 Nov 2008 17:45:59 -0800 (PST) [thread overview]
Message-ID: <6ef4285e-5be0-4a3c-bf6b-5b8882060688@h5g2000yqh.googlegroups.com> (raw)
In-Reply-To: mailman.133.1226494022.26697.help-gnu-emacs@gnu.org
Hi Alan,
thanks for your input. With the "debug-on-quit" option I could figure
out that the problem is related with the org-mode that I am using.
If I don't load org-mode, the imenu functionality is working also in
the
cc-mode.
Here is the stack trace that I get when org-mode is loaded.
Debugger entered--Lisp error: (quit)
byte-code( ... )
org-show-context(org-goto)
(lambda nil (org-show-context (quote org-goto)))()
run-hooks(imenu-after-jump-hook)
imenu(("dlgInputProc" . #<marker at 1512 in ScriptTester.c>))
call-interactively(imenu)
execute-extended-command(nil)
call-interactively(execute-extended-command)
org-mode has version 5.23a, it is the one that comes within Emacs
22.3:
org-version is a variable defined in `org.el'.
Its value is "5.23a"
I mentioned that I do not have these kind of problems when running
emacs 21.3. I should add here that for the old emacs version I did
download org-mode from the org-mode.org site and this is version
6.08c.
I have tried now several c files, also small ones, and it doesn' seem
to relate with the content or size of the c code file.
Next step I try to do is to upgrade the org-mode related files to
version 6.08 in emacs 22. Guess this would only be a question
of placing the newer files into a elisp directory that comes in the
path specification before the standard elisp library directories.
I am happy to help to fix this issue (if this is a bug). I just need
to understand a bit more how to file a bug.
On Nov 12, 1:58 pm, Alan Mackenzie <a...@muc.de> wrote:
> [ Reply-To: set to bug-cc-m...@gnu.org ]
>
> > It seems like the imenu related lisp code runs in some never-ending
> > loop. I guess it would help me a lot, if I can have some hints how to
> > activate the elisp debugger.
>
> The simplest ways are (setq debug-on-error t) and (setq debug-on-quit t).
> The second one seems the most relevant here. After setting
> debug-on-quit, get into the infinite loop and C-g it - this gets you into
> the debugger, with a display of the calling stack. The debugger is
> documented on the page "debugger" in the Elisp manual.
>
> --
> Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2008-11-13 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 11:21 imenu with cc-mode in emacs 22 (win32) Rudolfo Ungern
2008-11-12 12:58 ` Alan Mackenzie
[not found] ` <mailman.133.1226494022.26697.help-gnu-emacs@gnu.org>
2008-11-13 1:45 ` Rudolfo Ungern [this message]
2008-11-13 11:26 ` Rudolfo Ungern
2008-11-17 18:58 ` Rudolfo Ungern
2008-11-18 15:57 ` Rudolfo Ungern
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ef4285e-5be0-4a3c-bf6b-5b8882060688@h5g2000yqh.googlegroups.com \
--to=rolf_unger@hotmail.com \
--cc=bug-cc-mode@gnu.org \
--cc=help-gnu-emacs@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).