The vim-tidal plugin has a very raw patch that replaces the ghci command with the tidal command provided by this flake. This is done by patching the command string which assumes the tidal command is present.
Instead, we should use the full nix store path of this flake's tidal command in order to guarantee its availability. This involves making the tidal command a hard requirement for the vim-tidal plugin.
Similarly, we should replace the Tidal.ghci provided by the vim-tidal repo with the BootTidal.hs file directly from the tidal repo that is used to construct the ghc package used within our tidal command. This way we can guarantee the BootTidal.hs ghci script used in the Vim plugin is from the same tidal repo git commit as the Tidal library that is provided to ghc.
The
vim-tidalplugin has a very raw patch that replaces theghcicommand with thetidalcommand provided by this flake. This is done by patching the command string which assumes thetidalcommand is present.Instead, we should use the full nix store path of this flake's
tidalcommand in order to guarantee its availability. This involves making thetidalcommand a hard requirement for thevim-tidalplugin.Similarly, we should replace the
Tidal.ghciprovided by thevim-tidalrepo with theBootTidal.hsfile directly from the tidal repo that is used to construct theghcpackage used within ourtidalcommand. This way we can guarantee theBootTidal.hsghci script used in the Vim plugin is from the same tidal repo git commit as the Tidal library that is provided toghc.