From: David Engster <deng@randomsample.de>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 12045@debbugs.gnu.org
Subject: bug#12045: 24.1.50; semantic :: Debugger entered--Lisp error: (wrong-type-argument syntax-table-p nil)
Date: Thu, 11 Oct 2012 22:45:54 +0200 [thread overview]
Message-ID: <87txu0d9fh.fsf@engster.org> (raw)
In-Reply-To: <87393zrunv.fsf@gmail.com> (Jambunathan K.'s message of "Tue, 07 Aug 2012 13:38:36 +0530")
Jambunathan K. writes:
> My original report was on Windows. The current report is on Debian
> Squeeze against CEDET bzr repo. So, consider this a bug report against
> the "future"-CEDET.
>
> When I do "C-c , j" on some symbol, that I know is defined in current
> .el file, I get
> ,----
> | Jump to symbol: org-e-odt-lib-dir [No Match] [5 times]
> `----
>
> When I partially type up the symbol and do TAB for completion, I get
> ,----
> | semantic-analyze-current-context: Cannot analyze buffers not supported
> | by Semantic
> `----
>
> If semantic does not support EmacsLisp files [1],
> 1. It should report an error or warning when the buffer tries to enter
> semantic-mode.
>
> 2. Disable menu items (starting with Developement->etc) that doesn't
> apply to current buffer.
You are right, this problem still exists. It is due to the fact that
semantic-mode is active for all buffers (it is a minor mode after all),
whether they could be parsed or not. Raising an error or warning for all
buffers that cannot be parsed would surely be very annoying, so we
cannot do that. However, we can check if a buffer was parsed by calling
`semantic-active-p' (which simply returns `semantic-new-buffer-fcn-was-run').
The solution for the menu items is pretty simple (checking for
`semantic-active-p' instead of only looking at `semantic-mode'). I've
now pushed a change to CEDET upstream that does this, and I will merge
it soon.
Regarding interactive commands, especially those with a pre-defined
keybinding, I'm not entirely sure what would be the best fix. The
easiest way would be if keymaps could be activated dependend on a
buffer-local variable, just as I can do that via the :visible attribute
for menu items. I don't think this is possible, but maybe someone around
here knows a solution. Otherwise, we'd have to check for
`semantic-active-p' in all interactive commands.
-David
next prev parent reply other threads:[~2012-10-11 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 14:58 bug#12045: 24.1.50; semantic :: Debugger entered--Lisp error: (wrong-type-argument syntax-table-p nil) Jambunathan K
2012-07-25 21:13 ` David Engster
2012-07-27 20:25 ` Jambunathan K
2012-07-27 20:47 ` Achim Gratz
2012-07-28 7:03 ` Eli Zaretskii
2012-08-07 8:08 ` Jambunathan K
2012-10-11 20:45 ` David Engster [this message]
2012-10-11 21:04 ` David Engster
2012-10-12 0:08 ` Stefan Monnier
2012-10-12 6:10 ` David Engster
2012-10-12 13:47 ` Stefan Monnier
2012-10-14 19:41 ` David Engster
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=87txu0d9fh.fsf@engster.org \
--to=deng@randomsample.de \
--cc=12045@debbugs.gnu.org \
--cc=kjambunathan@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).