-
Notifications
You must be signed in to change notification settings - Fork 21
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
Release and development version both do not display preview #873
Comments
There are so many strange things, it is hard for me to even know where to start. The above shows that it is not finding any of our substitutions, yet that seems to be working fine and our build process builds everything. I uninstalled restructured text and esbonio, then installed them again. But the first time I run VSCode after the install, restructured text pops up a box that say it depends on " swyddfa.esbonio" and asks if I want to install it. So I say yes to install the pre-release version. But it doesn't seem to install it, it just goes to the extension screen so I install it there. When I click on preview, "Activating Extensions" appears in the task bar at the bottom with a spinning icon and goes away after 6 seconds. Nothing at all gets added to the log. |
Please split this into two (one for stable version, and the other for prerelease version). The two differ too much, so cannot be discussed together. Keep in mind that when "One of our team was able to get it working by switching to a different version of python", you should focus on that and replicate the settings to the rest of the team members. It's relatively easier to use the stable version, as its setup and troubleshooting is simpler. |
@FrightRisk Thanks for all the info!
I am a little confused about that, the logs you've included are the ones I would expect to see when running the release version... Anyway, the main culprit appears to be buried in the middle of the log output
It looks like either the If you need to you can use the
These messages will appear in the log when you click on the preview button with the Output panel focused. It's annoying, but you need to make sure you have the editor containing the
The errors about undefined substitutions are most likely due to how Esbonio is generating the symbols for the Outline view, in this case they're probably safe to ignore. Hope that helps! |
Yes that's likely the culprit, Esbonio will need your So that it can keep refreshing the preview as you work Esbonio will keep Sphinx running in the background and periodically trigger builds to regenerate the html files. It also relies on this background process to figure out where they live. I would try splitting your build script in two, one to create the
it looks like it's already setup to look for the right environment
Not sure why you are seeing both... perhaps the reStructuredText extension is creating its own channel? The one called
Sorry that's another red herring, I have some tools I use sometimes during development, that's just a message saying that they aren't available on your machine. |
I am still a bit lost. Now the box saying it can't find anything when I click preview doesn't do anything, I just get the "actvating extensions" spinning at the bottom for a few seconds. I create the venv and do not destroy it. I can see it open in my dos window. It looks like VSC is point to it and that is my environment in esbonio. I don't know if I need to install something else manually in the venv to make this work. I am just intalling and uninstalling the extensions in visual studio (rstructured text, python, esbonio). This is all I see in the debug level log:
|
Oh, it looks like you might have the |
Success! And looks like I can turn off building in my "venv_start.bat" file that I created since when I go into VSC for the first time after opening the venv and building the html docs, esbonio displays the "no files found" message. But since I still had debug logging on (turned it off for the server) it showed me it was building in the background. Once it completed, it just displayed the html version in the pane. I don't suppose I can run this on 2 monitors somehow with the preview pane detached and over on the other monitor, can I? ;) So bottom line is, open the venv, open VSC/PlatformIO, make sure the environment points to the venv. Open the pane so esbonio builds the first time. Enjoy. Then close and delete the folder for the venv and repeat as necessary. |
Glad to hear it! :)
That would depend on if VSCode supports a detached WebView... 🤔 I know they recently added support for detaching editors. So I guess it should be possible for you to detach the editor view and move the main VSCode window containing the preview over to the other monitor?
I'd say deleting the venv is optional, you'd typically only have to delete it when you wanted to create it from scratch - perhaps when updating all of your packages. |
Expected behavior
Expect that clicking the preview button will display a preview
Actual behavior
The release version does nothing and there is nothing in the log window. I will try to provide the extended log. One of our team was able to get it working by switching to a different version of python (3 showed up in their list). I tried using the development version and could get a a window to popup saying it could not find any files to display, but something I have done has made that go away. Under the development version, I see the log below using the extended logging
Log output
(Optional) Settings from conf.py
The text was updated successfully, but these errors were encountered: