-
Notifications
You must be signed in to change notification settings - Fork 22
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
reStructuredText ecosystem changes in 2024 #708
Comments
The very first change made in vscode-restructuredtext is that prerelease version 190.1.17 is shipped without live preview and language server features. Instead, this version recommends esbonio latest prerelease version to be installed. Once more testing is finished and no significant issue is there, a stable version will be published. |
Maybe a stupid question, but I can find the esbonio extension in the VSCode marketplace but not in VSCode itself. Am I missing something (e.g. I need VSCode >=1.86.0)? 😅 EDIT: installed it now using the .vsix file... But cannot get it up and running... |
At least, LeXtudio Inc. and all its VS Code extensions only support VS Code. VSCodium isn't a supported platform for us. |
Your VSCodium version should be fine, if I remember rightly the esbonio pre-release only requires 1.82.0+, so no idea why it's not showing for you sorry.
Glad to hear you managed to get it installed at least, are there any specific errors you can share? The first-run experience isn't the best at the moment... a common issue is that the extension isn't using the correct Python environment for your project, have you chosen one using the |
As far as I could see the esbonio server didn't even start to run (nothing in the Status Bar as with stable and no previews only an empty Preview). I didn't run the I already rolled back to stable. If you are interested in me trying it again I can do, but if you know about some kind of bugs I would leave it in it's current state 😅 |
Just released vscode-restructuredtext 190.2.0 stable release, and ended the transition tasks there. @alcarney More users will be driven toward the latest prerelease build of this Esbonio VS Code extension in the coming months. You might consider increasing release frequency to ship bugfixes quicker. BTW, my team is willing to help on bugfixes but we couldn't get the development environment stabilised. Will write to you via emails with more details. |
@lextm ok thanks, will keep that in mind...
Can't say I'm surprised, any docs that do exist about dev envs will be wildly out of date by this point 😅 |
@alcarney we didn't yet switch to devcontainer. Close this item now. If there are any future action items, will create new issues to track them. |
Esbonio evolves very fast, so it seems to be the right time to review the ecosystem and plan out the future for all end users.
I think the ideal arrangement in 2024 might look as below,
Features marked with
Y*
might be later migrated to esbonio if needed.Another important change we might consider is to host the documentation together, likely on restructuredtext.net.
The text was updated successfully, but these errors were encountered: