From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Engster <deng@randomsample.de>
Cc: Jambunathan K <kjambunathan@gmail.com>, 12045@debbugs.gnu.org
Subject: bug#12045: 24.1.50; semantic :: Debugger entered--Lisp error: (wrong-type-argument syntax-table-p nil)
Date: Fri, 12 Oct 2012 09:47:08 -0400 [thread overview]
Message-ID: <jwvmwzrhkjf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87haq0cj9x.fsf@engster.org> (David Engster's message of "Fri, 12 Oct 2012 08:10:50 +0200")
> Regarding the key bindings however, I think we can agree that the
> current situation needs improvement. The interactive commands usually
> assume that the buffer was correctly set up for parsing and hence raise
> some cryptic error if that isn't the case (see subject).
Right, the error message should be improved.
> So if the keybindings should simply stay enabled in all buffers if
> semantic-mode is active, I will have to add some
> `semantic-raise-error-if-unparsed' function at the beginning of every
> interactive function.
Also, compared to making the binding conditional, this has the advantage
that the error message can say *why* the binding doesn't work, contrary
to a laconic "<key> is undefined".
Stefan
next prev parent reply other threads:[~2012-10-12 13:47 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
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 [this message]
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=jwvmwzrhkjf.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=12045@debbugs.gnu.org \
--cc=deng@randomsample.de \
--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).