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
bug: compile error in unknown global in strict mode: vim #22
Comments
There was a bug fix in Fennel 0.10 with strict reporting, so that may be why you're seeing it in Hotpot, or Aniseed fiddles with the globals. These might be related: Are you using vim in a macro or just regular old fennel? I have no trouble accessing |
You're right. I got some |
Try |
I do plan to expose compiler configuration #14 which will let you pass options to Fennels compiler to avoid this. The reason I don't just set it up to allow Edit: Aniseed runs with the sandbox disabled which is why you don't see the error https://github.com/Olical/aniseed/blob/c364acfb58a2185e8cf6a0dc5ef91b0aa1024562/fnl/aniseed/compile.fnl#L29-L30 |
Thank you for details. IMO, it's worth to fix this, especially for new neovim users who want to use fennel for their config using |
Merged compiler options, see require("hotpot").setup({
compiler = {
macros = {
env = "_COMPILER",
compilerEnv = _G,
allowedGlobals = false,
}
}
}) Note you will still technically see errors in stderr until this commit is released in the next fennel release which fixes a bug in Fennel not actually propagating the options down to the compiler. |
Wow, that's great news. Thank you so much 😘 |
I got this error whenever I open
nvim
.Edit: I just want to confirm that this bug doesn't happen with
aniseed
using the samenvim config
The text was updated successfully, but these errors were encountered: