|
1 | | -{;; Enables verbose notifications from nfnl, including notifications about |
2 | | - ;; when it starts up and when it compiles successfully. Useful for debugging |
3 | | - ;; the plugin itself and checking that it's running when you expect it to. |
4 | | - :verbose false |
5 | | - |
6 | | - ;; When false, will not write the protective `-- [nfnl] ...` header to the resulting .lua files. |
7 | | - ;; It will also prevent nfnl from checking for this header before overwriting .lua files. |
8 | | - ;; Intended for users who wish to write shebang comments at the top of their .lua for easier execution. |
9 | | - :header-comment true |
10 | | - |
11 | | - :orphan-detection |
12 | | - {;; Automatically invoke :NfnlFindOrphans whenever you write to a .fnl file. This acts as a passive |
13 | | - ;; garbage collection check and will warn you about dangling .lua files left over from .fnl deletions or renames. |
14 | | - ;; If an orphan is found, you can use :NfnlDeleteOrphans to delete all of the files listed |
15 | | - ;; automatically. The deletion command will NOT prompt you, so make sure you check the list first! |
16 | | - :auto? true |
17 | | - |
18 | | - ;; If you embed nfnl, for example, in your Lua directory then nfnl will detect those files as orphans. |
19 | | - ;; You can add Lua patterns here to tell nfnl which Lua paths are okay and should not be counted as orphans. |
20 | | - ;; Example: ["lua/nfnl/"] |
21 | | - :ignore-patterns []} |
22 | | - |
23 | | - ;; Passed to fennel.compileString when your code is compiled. |
24 | | - ;; See https://fennel-lang.org/api for more information. |
25 | | - :compiler-options {;; Disables ansi escape sequences in compiler output. |
26 | | - :error-pinpoint false} |
27 | | - |
28 | | - ;; Warning! In reality these paths are absolute and set to the root directory |
29 | | - ;; of your project (where your .nfnl.fnl file is). This means even if you |
30 | | - ;; open a .fnl file from outside your project's cwd the compiler will still |
31 | | - ;; find your macro files. If you use relative paths like I'm demonstrating here |
32 | | - ;; then macros will only work if your cwd is in the project you're working on. |
33 | | - |
34 | | - ;; They also use OS specific path separators, what you see below is just an example really. |
35 | | - ;; I'm not including nfnl's directory from your runtimepath, but it would be there by default. |
36 | | - ;; See :rtp-patterns below for more information on including other plugins in your path. |
37 | | - |
38 | | - ;; String to set the compiler's fennel.path to before compilation. |
39 | | - :fennel-path "/home/.../?.fnlm;/home/.../?/init.fnlm;/home/.../fnl/?.fnlm;/home/.../fnl/?/init.fnlm;/home/.../?.fnl;/home/.../?/init.fnl;/home/.../?/init-macros.fnl;/home/.../fnl/?.fnl;/home/.../fnl/?/init.fnl;/home/.../fnl/?/init-macros.fnl" |
40 | | - |
41 | | - ;; String to set the compiler's fennel.macro-path to before compilation. |
42 | | - :fennel-macro-path "/home/.../?.fnlm;/home/.../?/init.fnlm;/home/.../fnl/?.fnlm;/home/.../fnl/?/init.fnlm;/home/.../?.fnl;/home/.../?/init.fnl;/home/.../?/init-macros.fnl;/home/.../fnl/?.fnl;/home/.../fnl/?/init.fnl;/home/.../fnl/?/init-macros.fnl" |
43 | | - |
44 | | - ;; A list of glob patterns (autocmd pattern syntax) of files that |
45 | | - ;; should be compiled. This is used as configuration for the BufWritePost |
46 | | - ;; autocmd, so it'll only apply to buffers you're interested in. |
47 | | - ;; Will use backslashes on Windows. |
48 | | - ;; Defaults to compiling all .fnl files, you may want to limit it to your fnl/ directory. |
49 | | - :source-file-patterns ["fnl/**/*.fnl"] |
50 | | -} |
| 1 | +(local core (require :eca.nfnl.core)) |
| 2 | +(local config (require :eca.nfnl.config)) |
| 3 | +(local defaults (config.default)) |
| 4 | + |
| 5 | +{:compiler-options (core.merge |
| 6 | + defaults.compiler-options |
| 7 | + {:compilerEnv _G}) |
| 8 | + :source-file-patterns [".nvim.fnl" "plugin/*.fnl" "fnl/**/*.fnl"] |
| 9 | + :orphan-detection {:ignore-patterns ["lua/eca/nfnl/"]}} |
0 commit comments