Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

imenu crash when in_ appears in variable name #7850

Closed
vicuna opened this issue Sep 19, 2018 · 4 comments
Closed

imenu crash when in_ appears in variable name #7850

vicuna opened this issue Sep 19, 2018 · 4 comments

Comments

@vicuna
Copy link

vicuna commented Sep 19, 2018

Original bug ID: 7850
Reporter: wyuenho
Status: new
Resolution: open
Priority: normal
Severity: minor
Category: emacs mode

Bug description

Discovered when trying out the PR for #7844.

Given this code:

module rec Foo : FOO = struct
  and in_hello =
    let b in
    in_hello (* error *)

This backtrace is given:

Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  buffer-substring-no-properties(nil nil)
  caml-match-string(5)
  tuareg-imenu-create-index()
  imenu--make-index-alist()
  imenu-list-rescan-imenu()
  imenu-list-collect-entries()
  imenu-list-update()
  purpose-x-code1-update-changed()
  #f(compiled-function () #<bytecode 0x45089141>)()
  apply(#f(compiled-function () #<bytecode 0x45089141>) nil)
  timer-event-handler([t 0 1 0 nil #f(compiled-function () #<bytecode 0x45089141>) nil idle 0])
@vicuna
Copy link
Author

vicuna commented Sep 28, 2018

Comment author: wilfred

See pull request: #2078

@vicuna
Copy link
Author

vicuna commented Oct 12, 2018

Comment author: wilfred

This can now be closed, as the PR has been merged.

@github-actions
Copy link

github-actions bot commented May 7, 2020

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.

@github-actions github-actions bot added the Stale label May 7, 2020
@xavierleroy
Copy link
Contributor

Closing as suggested by the original poster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants