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
It is my understanding that odoc can be used to produce LaTeX documentation, it would be nice to be able to download a pdf of the xyz documentation from ocaml.org/p/xyz.
ocaml.org/p/core can be quite slow sometimes, possibly this is is because the package is so large, with up to 5-10s to load the page for a package. I had a video call last night with a friend 1000s of kilometers away and there was a point when we were both just sitting there waiting for the documentation to load, certainly the time to load a webpage should be small compared to the lag of the video call.
If one wants to use the documentation constantly as a reference then waiting 5-10 seconds each time becomes irritating, and it becomes much more preferable to have local documentation.
The tool odig is available for local documentation and it seems to work well, but this is a somewhat convoluted solution for the group of Windows-based developers who use the WSL2 subsystem, as they have to figure out how to configure the Linux VM to launch a Windows web browser when odig doc xyz is called.
The text was updated successfully, but these errors were encountered:
It is my understanding that odoc can be used to produce LaTeX documentation, it would be nice to be able to download a pdf of the xyz documentation from ocaml.org/p/xyz.
ocaml.org/p/core can be quite slow sometimes, possibly this is is because the package is so large, with up to 5-10s to load the page for a package. I had a video call last night with a friend 1000s of kilometers away and there was a point when we were both just sitting there waiting for the documentation to load, certainly the time to load a webpage should be small compared to the lag of the video call.
If one wants to use the documentation constantly as a reference then waiting 5-10 seconds each time becomes irritating, and it becomes much more preferable to have local documentation.
The tool odig is available for local documentation and it seems to work well, but this is a somewhat convoluted solution for the group of Windows-based developers who use the WSL2 subsystem, as they have to figure out how to configure the Linux VM to launch a Windows web browser when odig doc xyz is called.
The text was updated successfully, but these errors were encountered: