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

[emacs] problem with showing type at error location #14

Closed
asmanur opened this issue Feb 21, 2013 · 1 comment
Closed

[emacs] problem with showing type at error location #14

asmanur opened this issue Feb 21, 2013 · 1 comment
Assignees
Labels

Comments

@asmanur
Copy link
Contributor

asmanur commented Feb 21, 2013

When asking for the type in a phrase with an error inside it, instead of doing nothing or reporting the error, it prints the type of the token of the last phrase (seemingly)

@ghost ghost assigned asmanur Feb 21, 2013
@let-def
Copy link
Contributor

let-def commented Feb 21, 2013

Yes you're right. This is an approximation while we have a better handling of contexts. You can always check that cursor is inside the returned location.

@asmanur asmanur closed this as completed Mar 6, 2013
catern pushed a commit to catern/merlin that referenced this issue May 6, 2024
* Import ocaml sources for ocaml-flambda/flambda-backend@9d77824d1

Signed-off-by: Nick Roberts <nroberts@janestreet.com>

* Initial commit with conflicts

Signed-off-by: Nick Roberts <nroberts@janestreet.com>

* Upgrade

Signed-off-by: Nick Roberts <nroberts@janestreet.com>

* Upgrade magic numbers and add new flags

Signed-off-by: Nick Roberts <nroberts@janestreet.com>

* Delete output of merge

Signed-off-by: Nick Roberts <nroberts@janestreet.com>

* Fix shift/reduce conflicts

Signed-off-by: Nick Roberts <nroberts@janestreet.com>

* Remove stray merge file

Signed-off-by: Nick Roberts <nroberts@janestreet.com>

---------

Signed-off-by: Nick Roberts <nroberts@janestreet.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants