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

VS Code extension does not use selene.toml from outside of its folder #611

Open
LordOfSpelunky opened this issue Jul 11, 2024 · 0 comments · May be fixed by #543
Open

VS Code extension does not use selene.toml from outside of its folder #611

LordOfSpelunky opened this issue Jul 11, 2024 · 0 comments · May be fixed by #543
Labels
A-bin Area: selene, the program C-enhancement Category: Feature request or improvement

Comments

@LordOfSpelunky
Copy link

LordOfSpelunky commented Jul 11, 2024

If you have a file structure with A/B/C.lua, and A/selene.toml, if you open up the folder B in VS Code, then it will not use the selene.toml. I think this is a result of pwd being used for selene.toml, I forget if it is based on ancestry in any way yet.

@chriscerie chriscerie added C-enhancement Category: Feature request or improvement A-bin Area: selene, the program labels Jul 12, 2024
@chriscerie chriscerie linked a pull request Jul 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-bin Area: selene, the program C-enhancement Category: Feature request or improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants