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

Autocomplete stops working when accessing table contents of love.filesystem.getInfo #20

Open
HugoBDesigner opened this issue Feb 13, 2021 · 3 comments

Comments

@HugoBDesigner
Copy link

This bug seems to be specifically and uniquely related to the love.filesystem.getInfo call. Unlike other LÖVE calls, this one returns a table with named fields inside of it. As soon as any field is accessed in the results (not necessarily an existing field, but just a field from the results), the entire autocomplete suite (not just love-atom) stops responding after the first character is typed.

The same issue does not occur if you call any other function that returns a table. I've also tested writing my own function that returned a table with named fields, but it works fine. Accessing these fields using brackets does not solve the issue. Disabling the love-atom package does solve the issue.

2021-02-13_18-41-17.mp4
@rm-code
Copy link
Owner

rm-code commented Feb 14, 2021

@HugoBDesigner Thanks for the report, unfortunately I don't have the time to look at this properly. On a quick test of mine I think I also could reproduce it with love.graphics.getSupported which might point to a deeper problems with functions that return tables.

It might be possible that the autocomplete-lua package got some update that broke love-atom, but I'd have to investigate. I haven't been using Atom for a couple of years and would really appreciate if somebody would take over this package. Sorry.

@rm-code
Copy link
Owner

rm-code commented Feb 14, 2021

Maybe @pablomayobre or @JanWerder could help?

@JanWerder
Copy link
Contributor

I'm sorry, but I haven't used Atom in ages, either.

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

No branches or pull requests

3 participants