help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

csharp-mode from Melpa: Invalid search bound (wrong side of point)


From: Steinar Bang
Subject: csharp-mode from Melpa: Invalid search bound (wrong side of point)
Date: Fri, 29 May 2015 12:32:13 +0200
User-agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/24.4 (windows-nt)

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.

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?

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]*\\(base\\|this\\)\\)[   \n.\f]*(" 
33498 t)
  #[(limit) "\304\301!\305.\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)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]