-
I have a lot of macros in its own repo that i wanna make sure that they end up as i desire (especially if i simplify or expand the macro). attempting to use aniseed-testing doesn't seem to ever run the tests i've tried the following in its appropriately placed testing location, and the test never runs (module katcros-fnl.macros.nvim.api.autocommands.macros-test
{import-macros [[kat :katcros-fnl.macros.nvim.api.autocommands.macros]]})
(deftest macro-cle-auc!
(t.pr= (vim.api.nvim_clear_autocmds {}) (kat.cle-auc! {}))) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
Hehe, Another thing that should just work in nfnl (although it may be infeasible for you for other reasons of course). I assume these are working fine outside of tests? (silly question, but just want to be sure) |
Beta Was this translation helpful? Give feedback.
OH NO, I just worked it out I think! Try renaming both occurrences of
macros
tomacnos
It's because Aniseed is seeing the path with the word "macro" in it and deciding not to compile the fnl because it thinks it's also a macro file and can not be compiled. Again, nfnl doesn't have this issue because you tag your macro files with a comment instead of relying on naming conventions.