[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: csharp-mode from Melpa: Invalid search bound (wrong side of point)
From: |
Alan Mackenzie |
Subject: |
Re: csharp-mode from Melpa: Invalid search bound (wrong side of point) |
Date: |
29 May 2015 12:56:29 -0000 |
User-agent: |
tin/2.2.0-20131224 ("Lochindaal") (UNIX) (FreeBSD/10.1-RELEASE (amd64)) |
Hello, Steinar.
In article <mailman.3893.1432895554.904.help-gnu-emacs@gnu.org> you wrote:
> Platform: Win7 x64
> GNU Emacs 24.4.1 (i686-pc-mingw32) of 2014-10-24 on LEG570
> csharp-mode 20150514.251 (from Melpa)
> I've pulled in csharp-mode from Melpa, and when I do 'M-x occur' in a
> buffer in csharp-mode I get the error message: Invalid search bound (wrong
> side of point)
> See also the error stack trace below.
The stack trace is most revealing: it looks like a fontification bug in CC
Mode (of which csharp-mode is a derivative).
> Has anyone else seen something similar, and/or know what might be
> causing it, and might have an idea how to fix it in csharp-mode or find
> a workaround?
Usual questions for an Emacs bug: does the bug happen when you start with
emacs -Q (followed by "manually" loading csharp-mode)? Does the bug
happen in Emacs 24.5 or in the latest development trunk version (if you
have easy access to this - I think you have)?
If the answer to the last question is "yes", could you please report this
as an Emacs bug (e.g., by posting to bug-gnu-emacs@gnu.org), and include,
in addition to what is in your post here:
1. A copy of a C# file which triggers the bug (or a URL where the file
can be found). The smaller this file is, the easier for the maintainer.
2. A complete recipe, starting preferably from emacs -Q, on how to
reproduce the bug.
3. If you need your own CC Mode settings to trigger the bug, then a dump
of your CC Mode configuration created by C-c C-b from the C# Mode buffer.
> Thanks!
> - Steinar
> Error stack trace from 'M-x occur' in csharp-mode:
> Debugger entered--Lisp error: (error "Invalid search bound (wrong side of
> point)")
> re-search-forward("\\(:[ \n.\f^K]*\\(base\\|this\\)\\)[ \n.\f^K]*("
> 33498 t)
> #[(limit) "\304\301!\305.^Y\306\307\n\310#\203\221
> font-lock-fontify-keywords-region(33439 33498 nil)
> font-lock-default-fontify-region(33439 33498 nil)
> c-font-lock-fontify-region(33439 33498 nil)
> font-lock-fontify-region(33439 33498)
> run-hook-with-args(font-lock-fontify-region 33439 33498)
> #[0 "\302\303\300\242\301\242#\207" [(33439) (33498) run-hook-with-args
> jit-lock-functions] 4 "\n\n(fn)"]()
> funcall(#[0 "\302\303\300\242\301\242#\207" [(33439) (33498)
> run-hook-with-args jit-lock-functions] 4 "\n\n(fn)"])
> jit-lock-fontify-now(33439 33497)
> occur-engine-line(33439 33497 t)
> occur-engine("marked" (#<buffer Pakning.cs>) #<buffer *Occur*> 0 t underline
> shadow match t)
> occur-1("marked" nil (#<buffer Pakning.cs>))
> occur("marked" nil)
> call-interactively(occur record nil)
> command-execute(occur record)
> execute-extended-command(nil "occur")
> call-interactively(execute-extended-command nil nil)
> command-execute(execute-extended-command)
Thanks in advance!
--
Alan Mackenzie (Nuremberg, Germany).