Closed rrrnld closed 9 months ago
@mitchmindtree from what i can see you added the feature. do you have any thoughts on this?
I'm not too sure off the top of my head :thinking:
To help debug, could you try running Vim with the plugin (as opposed to neovim) and report back?
I'm a little less familiar with neovim - were you able to add the regular vim-tidal
vim plugin exposed by tidalcycles.nix as a plugin for your neovim?
Could you also echo g:tidal_ghci
? It should be the expansion of this: https://github.com/mitchmindtree/tidalcycles.nix/blob/1b1c4df5303e07930d23e8361ab8253ebec0c7bb/flake.nix#L130
I've tried to reproduce this with https://github.com/heyarne/vim-tidal-repro, but failed. Neovim and vim built using the flake in that repository both work fine. I therefore think this is not an issue of the vim-plugin, and will be moving to https://github.com/mitchmindtree/tidalcycles.nix/issues/20
I'd like to customize my
BootTidal.hs
. I set upvim-tidal
globally as a neovim plugin through https://github.com/mitchmindtree/tidalcycles.nix via home-manager (I have also opened an issue in the tidalcycles.nix repo in case the issue is somehow caused there: https://github.com/mitchmindtree/tidalcycles.nix/issues/20)When opening a directory with a
BootTidal.hs
, the path seems to be set OK (tested via:echo g:tidal_boot
), but the prompt that appears when evaluating the first expression always starts like this:This happens regardless of whether I use the
BootTidal.hs
discovery via directory traversal, open neovim vianvim --cmd ':let g:tidal_boot="/path/to/custom/BootTidal.hs"' test.tidal
, vianvim +':let g:tidal_boot="/path/to/custom/BootTidal.hs"' test.tidal
orexport TIDAL_BOOTH_PATH=…
. Am I missing something?Thanks for any help!