Auto compile on save only works if nvim current directory is under .nfnl.fnl file directory.

[Kethku]

After #36 I am able to manually compile and the autocompile on save is working but only works if neovim's current directory is in one that contains the .nfnl.fnl file or a child directory under a directory that contains a .nfnl.fnl file.

I had it in my head that this wasn't a requirement before I updated but it may be I'm misunderstanding it?

[Olical]

This should be the case and I can compile-on-write .fnl files from another working directory. So in my home dir I can open one of nfnl's files and write to it, the changes are reflected in the Lua. Would you be able to share your .nfnl.fnl file? Just in case it's something custom in there?

[Olical]

Is this still an issue for you? Because I couldn't reproduce it earlier, I can try again with the same specific Neovim version as you if you let me know which one you're on. Maybe it's an OS thing though 🤔

[Kethku]

Sorry I took so long to respond here. I'm very confident that this is an os thing. My .nfnl.fnl file is {}

[Kethku]

I'm attempting to fix this once and for all here #42

[Olical]

Ah okay! Thanks for looking into this! I'll take a look at the PR. I should really try and get some sort of nvim setup working on my gaming PC so I can test some things on Windows, not sure where to start really. I thought most people used WSL but that's just a Linux VM so there should be no work there.

Not sure how dotfiles even work for Neovim on Windows? I guess I'd need to write some config from scratch as a test bed because my personal one definitely won't work there.