Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HelpBrowser doesn't automatically render Help pages #33

Closed
dvzrv opened this issue Apr 29, 2017 · 1 comment
Closed

HelpBrowser doesn't automatically render Help pages #33

dvzrv opened this issue Apr 29, 2017 · 1 comment

Comments

@dvzrv
Copy link
Member

dvzrv commented Apr 29, 2017

When launching the HelpBrowser on a keyword through vim (ctrl+K), the HelpBrowser renders the HTML Help page for the keyword using SCDoc and opens it (HelpBrowser.openHelpFor("keyword");).
Inside the HelpBrowser however, this doesn't apply and thus clicking on links for keywords, that have not been rendered yet, does nothing.
Is there any way to change this? It's pretty annoying to use the HelpBrowser this way.
SCIDE does this on the fly. I wonder, in what way this can be changed when using scvim, as the HelpBrowser is launched as a singleton.

On a different note: It would be great to have the HelpBrowser stay open even between recompiles, or re-open the last opened Help page on recompile. Currently it is closed, as the sclang process launching it is killed.

@capocasa
Copy link
Member

capocasa commented Nov 7, 2019

Yeah that would be cool.

This sounds a little out-of-scope though- I wouldn't know how to fix the help browser from within scvim, because it's just a rather thin wrapper for sclang. So I'm passing the buck to sclang on this one- please reproduce when opening a help file directly from sclang and report there.

According to community enthusiasm (as perceived by me) scvim community would prefer to focus on fixing help browser related problems by switching to vim native help. Therefore, considering this a duplicate of #46.

@capocasa capocasa closed this as completed Nov 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants