-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
import-macro
uses nvim cwd and not project cwd.
#12
Comments
Require should be okay since it's runtime, import-macros and the include thing that inlines a require are compile time and will need some configuring. Investigating! |
This should be fixed, it seems to be for me + in the e2e test suite. Let me know and reopen if not! |
Actually, not 100% sure yet, the tests look good but I think it might still be borked. |
Okay, what do you think? |
I think it's fixed! my example usecase works entirely. thanks so much! |
simple test:
mkdir test touch test/{macro,.nfnl,file}.fnl
test/macro.fnl
test/file.fnl
cd ~; nvim test/file.fnl -c ':w'
cd test; nvim file.fnl -c ':w'
I would have perhaps expected something like:
test/file.fnl
.nfnl.fnl
.nfnl.fnl
is in) to act as the dir to resolve macro imports for.Usecase:
I want to be able to work on my projects, get the feel for a new config, edit the file from my current working directory (ie: inside a work project), and then save and compile my config before going back to what i was working on
this might also affect
require
calls but i'm not sure.The text was updated successfully, but these errors were encountered: