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

The reStructureText extension preview functionality is defunct. The reStructureText team says this is esbonio issue. #871

Open
MartinCupak opened this issue Aug 12, 2024 · 5 comments
Labels
bug Something isn't working triage Issues needing triage

Comments

@MartinCupak
Copy link

MartinCupak commented Aug 12, 2024

Expected behavior

In MS VS code, I expect functionality as per the animated gif on reStructuredText main page.

Actual behavior

no preview displayed.

Just open the .rst file and click on icon to "Open preview to the side", that does nothing.

Note: I have reported this at reStructureText github repo first. However, the reStructureText team says this is esbonio issue, hence reporting here.
(vscode-restructuredtext/vscode-restructuredtext#450)

Log output

N/A - nothing printed at all in the vs code output or debug console

(Optional) Settings from conf.py

Esbonio information
v0.11.0

reStructuredText
v190.4.1

Visual Studio Code information
Version: 1.92.0 Commit: b1c0a14de1414fcdaa400695b4db1c0799bc3124 Date: 2024-07-31T23:26:45.634Z Electron: 30.1.2 ElectronBuildId: 9870757 Chromium: 124.0.6367.243 Node.js: 20.14.0 V8: 12.4.254.20-electron.0 OS: Linux x64 5.15.0-117-generic

Operating system information
Linux Ubuntu 20.04LTS

Python information
3.9.19
@MartinCupak MartinCupak added bug Something isn't working triage Issues needing triage labels Aug 12, 2024
@MartinCupak MartinCupak changed the title The reStructureText team says this vs code reStructuredText extension behaviour is esbonio issue. The reStructureText team says this VS code reStructuredText extension behaviour is esbonio issue. Aug 13, 2024
@MartinCupak MartinCupak changed the title The reStructureText team says this VS code reStructuredText extension behaviour is esbonio issue. The reStructureText extension is defunct. The reStructureText team says this is esbonio issue. Aug 13, 2024
@FrightRisk
Copy link

We have not been able to use the Esbonio preview for months. Last week, we could see errors in the log about versions of "doc8" and "rstcheck" so we updated to later versions in our requirements.txt file and don't see any debug info. Clicking the preview icon does nothing.

@lextm
Copy link
Contributor

lextm commented Aug 13, 2024

@FrightRisk please create your own issue and follow the wizard to provide necessary information. Lingering under another issue doesn't help much as your case can be different in several ways.

@MartinCupak MartinCupak changed the title The reStructureText extension is defunct. The reStructureText team says this is esbonio issue. The reStructureText extension preview functionality is defunct. The reStructureText team says this is esbonio issue. Aug 13, 2024
@alcarney
Copy link
Member

@MartinCupak it's a hard to offer much advice without any logs.

The server is very quiet by default, you can try setting esbonio.server.logLevel to debug and running the Esbonio: Restart Language Server command from the command palette. You should then (hopefully!) see more information in the Esboino channel in the VSCode's Output panel.

In general however, in order to have a working preview you will need

  • to make sure VSCode is using the same Python environment you use when building your docs outside of VSCode. You can use the Python: Select interpreter command to change it, or bypass the Python extension entirely by setting esbonio.server.pythonPath

  • the esbonio Python package needs to be installed into the same Python environment you selected in the previous step. (Though the extension should offer to install it for you if required.)

  • the extension will need to have managed to do a complete build of your docs without crashing (you will have to check the logs for details)

Hope that helps!

@MartinCupak
Copy link
Author

Thanks, @alcarney, I'll give it a go once I have those extra 10 minutes for it ;-)

@lextm
Copy link
Contributor

lextm commented Sep 23, 2024

BTW, you shouldn't be using the old 0.11 release. The new 0.95.2 works very well for me. Check out #899 for more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Issues needing triage
Projects
None yet
Development

No branches or pull requests

4 participants