You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At a minimum we can make this location configurable, i.e. let g:psc_ide_source_glob='.psc-package/<package-set>'. But a better solution would be to look at the psc-package.json file and extract the value of set to create the path .psc-package/<package-set>.
A workaround for this issue at the moment is to create a symlink from bower_components to the package set. For me the command was ln -s .psc-package/psc-0.12.2 bower_components
The text was updated successfully, but these errors were encountered:
For psc-package the purs files are in
.psc-package/<package-set>
but the plugin is looking inbower_components
.psc-ide-vim/ftplugin/purescript_pscide.vim
Line 227 in 6d4a3cc
At a minimum we can make this location configurable, i.e.
let g:psc_ide_source_glob='.psc-package/<package-set>'
. But a better solution would be to look at thepsc-package.json
file and extract the value ofset
to create the path.psc-package/<package-set>
.A workaround for this issue at the moment is to create a symlink from
bower_components
to the package set. For me the command wasln -s .psc-package/psc-0.12.2 bower_components
The text was updated successfully, but these errors were encountered: