Compilation result differs from `macrodebug` result about hotpot.nvim HOT 13 CLOSED

I deleted that comment as I'm not tooooo sure how related they really are. That other issue was to do with re-evaluating macros repeatedly where as this seems to happen on the first call.

from hotpot.nvim.

After a test this seems to be an issue with Fennel itself, so I will open a new issue on the Fennel repository.

from hotpot.nvim.

Here is the issue on the Fennel repository: bakpakin/Fennel#425

from hotpot.nvim.

https://todo.sr.ht/~technomancy/fennel/110 Related

from hotpot.nvim.

https://todo.sr.ht/~technomancy/fennel/110 Related

Thanks! I will link it on the issue in the Fennel repository

from hotpot.nvim.

Nvm, you already linked it. Thanks!

from hotpot.nvim.

Gonna close this out as it's upstream and any fix will come through via (hopefully) the next Fennel release.

If a fix lands and you want to run a custom build before any release, you just have to replace lua/hotpot/fennel.lua with your own build and apply a tiny patch as shown here: a1b2775 (Edit: actually you also have to bump the internal plugin version or fennel will complain, and then have to rebuild Hotpot.)

Feel free to ping for help or if a new release happens and I don't notice.

from hotpot.nvim.

Thanks!

from hotpot.nvim.

Quick question related to this: does hotpot have any way to specify which version of Fennel to use?

The fix for this is already merged into the Fennel repo, but I can't use it yet with Hotpot.

from hotpot.nvim.

(assuming non-nix env):

1. Build your own fennel.lua file
2. Drop it into lua/hotpot/fennel.lua
3. Edit lua/hotpot/fennel.lua and replicate this patch a1b2775, the line numbers wont be the same but the surrounding context should be easy to find, it's inside SPECIALS["require-macros"] = function....
4. Edit lua/hotpot/searcher/module.lua and find versions = {"1.1.1"} and replace it with versions = {"1.2.0"}

I have actually been thinking it would be nice to have a branch that automatically tracks fennel-head, so I will probably try rigging some CI for that some time.

Alternatively you can clone, update deps/fennel.lua link, patch the file, run build.sh watch, patch the version in the fennel and adjust your nvim plugin stuff to use your local clone. Probably no harder just to patch the first way though.

Possibly there could be a way to set a global flag before hotpot loads to instruct it to get fennel from not hotpot.fennel but you'd get compiler warnings because of the plugin version mismatch - you'd still have to go patch the searcher anyway - and I think 99% of the time people wouldn't need it (esp if there were an actual HEAD branch).

from hotpot.nvim.

Thank you!

from hotpot.nvim.

Theoretically you can now track the nightly branch which theoretically should incorporate the latest upstream fennel each day (if there are any changes to merge).

The original idea was to run the test suite against any upcoming releases, you should be fine to just point your plugin manager at it but I can't promise I wont delete & recreate or rename the branch at some point. So I guess lock that fact away in your brain in case something explodes one day.

from hotpot.nvim.

Thank you! No problem with that, at least there is a way to manually patch it.

from hotpot.nvim.