When vim (or gvim) is launched in Windows, the current directory is the Windows 'My Documents' directory (unless vim has been configured differently.)
More often than not, there will NOT be forest/kelps files in that particular directory. That means that :Kelp will report a missing forest file when you run it in an empty vim screen.
vim doesn't know where forest is until you open a source file.
Hope this heads off some confusion. I think the message about the forest file is sufficient, but I wanted to make it clear what is going on.
I could add something to the plugin to make this plain -- any suggestions if this is necessary?
Thanks,
Dave Harris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When vim (or gvim) is launched in Windows, the current directory is the Windows 'My Documents' directory (unless vim has been configured differently.)
More often than not, there will NOT be forest/kelps files in that particular directory. That means that :Kelp will report a missing forest file when you run it in an empty vim screen.
vim doesn't know where forest is until you open a source file.
Hope this heads off some confusion. I think the message about the forest file is sufficient, but I wanted to make it clear what is going on.
I could add something to the plugin to make this plain -- any suggestions if this is necessary?
Thanks,
Dave Harris